The move has been postponed. We ran into a technical issue. We hope to try again next week. I will update this post when we finalized the schedule.
On January 16, 2019 at 5:00PM PDT, the PowerShell-Docs repositories are moving 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.
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:
git remote set-url origin new_url
For more information, see Changing a remote’s URL.
Which repositories are being moved?
The following repositories are being transferred:
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.
Senior Content Developer for PowerShell