d7cf81b64d
* Added functionality to improve failure triaging - Nunit logs will be created to tests. - Logs are copied to the Azure share. - Pester is run with -Quiet - Elevated and unelevated runs for tests with appropriate tags * Copy logs to Azure share and upload to CodeCov - Zip and copy to Azure log share - Upload to codecov using cygwin * Fixed varaible name in if condition * Addressed code review comments * Modified the destination folder structure for logs - Creates a folder structure for yyyy-MM and Windows for storing logs - Updated zip file name to not have illegal characters * Modifications as suggested by codecov.io |
||
|---|---|---|
| .github | ||
| .vscode | ||
| assets | ||
| demos | ||
| docker | ||
| docs | ||
| src | ||
| test | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .spelling | ||
| .travis.yml | ||
| appveyor.yml | ||
| build.psm1 | ||
| build.sh | ||
| CHANGELOG.md | ||
| codecov.yml | ||
| global.json | ||
| LICENSE.txt | ||
| license_thirdparty_proprietary.txt | ||
| nuget.config | ||
| powershell.sln | ||
| README.md | ||
| ThirdPartyNotices.txt | ||
PowerShell
Welcome to the PowerShell GitHub Community! PowerShell is a cross-platform (Windows, Linux, and macOS) automation and configuration tool/framework that works well with your existing tools and is optimized for dealing with structured data (e.g. JSON, CSV, XML, etc.), REST APIs, and object models. It includes a command-line shell, an associated scripting language and a framework for processing cmdlets.
New to PowerShell?
If you are new to PowerShell and would like to learn more, we recommend reviewing the getting started documentation.
Get PowerShell
You can download and install a PowerShell package for any of the following platforms.
| Platform | Downloads | How to Install |
|---|---|---|
| Windows 10 / Server 2016 (x64) | .msi | Instructions |
| Windows 8.1 / Server 2012 R2 (x64) | .msi | Instructions |
| Windows 7 (x64) | .msi | Instructions |
| Windows 7 (x86) | .msi | Instructions |
| Ubuntu 16.04 | .deb | Instructions |
| Ubuntu 14.04 | .deb | Instructions |
| CentOS 7 | .rpm | Instructions |
| macOS 10.11 | .pkg | Instructions |
| Docker | Instructions |
To install a specific version, visit releases.
Chat Room
Want to chat with other members of the PowerShell community?
We have a Gitter Room which you can join below.
There is also the community driven PowerShell Slack Team which you can sign up for at Slack Signup.
Building the Repository
| Linux | Windows | macOS |
|---|---|---|
| Instructions | Instructions | Instructions |
If you have any problems building, please consult the developer FAQ.
Build status of master branches
| AppVeyor (Windows) | Travis CI (Linux / macOS) |
|---|---|
 |
Build status of nightly builds
| AppVeyor (Windows) | Code Coverage Status |
|---|---|
 |
Downloading the Source Code
The PowerShell repository has a number of other repositories embedded as submodules.
To make things easy, you can just clone recursively:
git clone --recursive https://github.com/PowerShell/PowerShell.git
If you already cloned but forgot to use --recursive, you can update submodules manually:
git submodule update --init
See working with the PowerShell repository for more information.
Developing and Contributing
Please see the Contribution Guide for how to develop and contribute.
If you have any problems, please consult the known issues, developer FAQ, and GitHub issues. If you do not see your problem captured, please file a new issue and follow the provided template. If you are developing .NET Core C# applications targeting PowerShell Core, please check out our FAQ to learn more about the PowerShell SDK NuGet package.
Also make sure to check out our PowerShell-RFC repository for request-for-comments (RFC) documents to submit and give comments on proposed and future designs.
Legal and Licensing
PowerShell is licensed under the MIT license.
Governance
Governance policy for PowerShell project is described here.
Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.