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.
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.
- 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.
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
- 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
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 (Sean Wheeler) . GitHub
Source: The PowerShell-Docs repo is moving | PowerShell Team Blog
My Computer
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- Self built custom
- OS
- 64-bit Windows 11 Pro for Workstations
- CPU
- Intel i7-8700K OC'd to 5 GHz
- Motherboard
- ASUS ROG Maximus XI Formula Z390
- Memory
- 64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz
- Graphics Card(s)
- ASUS ROG-STRIX-GTX1080TI-O11G-GAMING
- Sound Card
- Integrated
- Monitor(s) Displays
- 2 x Samsung Odyssey G7 27"
- Screen Resolution
- 2560x1440
- Hard Drives
- 1TB Samsung 990 PRO M.2,
4TB Samsung 990 PRO PRO M.2,
TerraMaster F8 SSD Plus NAS
- PSU
- Seasonic Prime Titanium 850W
- Case
- Thermaltake Core P3
- Cooling
- Corsair Hydro H115i
- Keyboard
- Logitech wireless K800
- Mouse
- Logitech MX Master 4
- Internet Speed
- 2 Gb/s Download and 100 Mb/s Upload
- Antivirus
- Malwarebyte Anti-Malware Premium
- Browser
- Google Chrome
- Other Info
- Logitech Z625 speaker system,
Logitech BRIO 4K Pro webcam,
HP Color LaserJet Pro MFP M477fdn,
APC SMART-UPS RT 1000 XL - SURT1000XLI,
Galaxy S23 Plus phone