The PowerShell-Docs repositories have been moved from the PowerShell organization 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.
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. For more information, see Changing a remote’s URL.
The following example shows how to change the “upstream” remote to point to the new location:
[Wed 06:08PM] [staging =] PS C:\Git\PS-Docs\PowerShell-Docs> git remote -v origin https://github.com/sdwheeler/PowerShell-Docs.git (fetch) origin https://github.com/sdwheeler/PowerShell-Docs.git (push) upstream https://github.com/PowerShell/PowerShell-Docs.git (fetch) upstream https://github.com/PowerShell/PowerShell-Docs.git (push) [Wed 06:09PM] [staging =] PS C:\Git\PS-Docs\PowerShell-Docs> git remote set-url upstream https://github.com/MicrosoftDocs/PowerShell-Docs.git [Wed 06:10PM] [staging =] PS C:\Git\PS-Docs\PowerShell-Docs> git remote -v origin https://github.com/sdwheeler/PowerShell-Docs.git (fetch) origin https://github.com/sdwheeler/PowerShell-Docs.git (push) upstream https://github.com/MicrosoftDocs/PowerShell-Docs.git (fetch) upstream https://github.com/MicrosoftDocs/PowerShell-Docs.git (push)
Which repositories were moved?
The following repositories were 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
https://github.com/sdwheeler
Senior Content Developer for PowerShell
https://github.com/sdwheeler