• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

The Microsoft PowerShell-Docs repo is moving


On January 16, 2019 at 5:00PM PDT, the PowerShell-Docs repositories are moving from the PowerShellorganization to the MicrosoftDocs organization in GitHub.

The tools we use to build the documentation are designed to work in the MicrosoftDocs org. Moving the repository lets us build the foundation for future improvements in our documentation experience.

Impact of the move

During the move there may be some downtime. The affected repositories will be inaccessible during the move process. Also, the documentation processes will be paused. After the move, we need to test access permissions and automation scripts.

After these tasks are complete, access and operations will return to normal. GitHub automatically redirects requests to the old repo URL to the new location.

For more information about transferring repositories in GitHub, see About repository transfers.
  • If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete.
  • All Git information about commits, including contributions, are preserved.
  • All of the issues and pull requests remain intact when transferring a repository.
  • All links to the previous repository location are automatically redirected to the new location.
When you use git clone, git fetch, or git push on a transferred repository, these commands will redirect to the new repository location or URL.

However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using git remote on the command line:

[c]git remote set-url origin new_url[/c]

For more information, see Changing a remote’s URL.

Which repositories are being moved?

The following repositories are being transferred:
  • PowerShell/PowerShell-Docs
  • PowerShell/powerShell-Docs.cs-cz
  • PowerShell/powerShell-Docs.de-de
  • PowerShell/powerShell-Docs.es-es
  • PowerShell/powerShell-Docs.fr-fr
  • PowerShell/powerShell-Docs.hu-hu
  • PowerShell/powerShell-Docs.it-it
  • PowerShell/powerShell-Docs.ja-jp
  • PowerShell/powerShell-Docs.ko-kr
  • PowerShell/powerShell-Docs.nl-nl
  • PowerShell/powerShell-Docs.pl-pl
  • PowerShell/powerShell-Docs.pt-br
  • PowerShell/powerShell-Docs.pt-pt
  • PowerShell/powerShell-Docs.ru-ru
  • PowerShell/powerShell-Docs.sv-se
  • PowerShell/powerShell-Docs.tr-tr
  • PowerShell/powerShell-Docs.zh-cn
  • PowerShell/powerShell-Docs.zh-tw
Call to action

If you have a fork that you cloned, change your remote configuration to point to the new upstream URL.

Help us make the documentation better.
  • Submit issues when you find a problem in the docs.
  • Suggest fixes to documentation by submitting changes through the PR process.

Sean Wheeler
Senior Content Developer for PowerShell
sdwheeler - Overview

Source: The PowerShell-Docs repo is moving | PowerShell Team Blog

My Computer

System One

  • OS
    64-bit Windows 10
    Computer type
    System Manufacturer/Model Number
    Custom self built
    Intel i7-8700K OC'd to 5 GHz
    ASUS ROG Maximus XI Formula Z390
    16 GB (8GBx2) G.SKILL TridentZ DDR4 3200 MHz
    Graphics Card(s)
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    3 x 27" Asus VE278Q
    Screen Resolution
    Hard Drives
    250GB Samsung 960 EVO M.2,
    256GB OCZ Vector,
    6TB WD Black WD6001FZWX
    8TB WD MyCloudEX2Ultra NAS
    OCZ Series Gold OCZZ1000M 1000W
    Thermaltake Core P3
    Corsair Hydro H115i
    Logitech wireless K800
    Logitech MX Master
    Internet Speed
    1 Gb/s Download and 35 Mb/s Upload
    Internet Explorer 11
    Malwarebyte Anti-Malware Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    Linksys EA9500 router,
    Arris SB8200 cable modem,
    Lumia 1520 phone

Users Who Are Viewing This Thread (Users: 0, Guests: 1)