PowerShellGet is a PowerShell module with commands for discovering, installing, updating and publishing the PowerShell artifacts like Modules, DSC Resources, Role Capabilities and Scripts.
PowerShellGet module is also integrated with the PackageManagement module as a provider, users can also use the PackageManagement cmdlets for discovering, installing and updating the PowerShell artifacts like Modules and Scripts.
| AppVeyor (Windows - PS & PSCore) | Travis CI (Linux / macOS) |
|---|---|
 |
| AppVeyor (Windows - PS & PSCore) | Travis CI (Linux / macOS) |
|---|---|
 |
- Windows PowerShell 3.0 or newer.
- PowerShell Core.
- PackageManagement module
# On PowerShell 5.0 or newer, use the Install-Module with -Force to install the PowerShellGet module from the PowerShellGallery.
Install-Module -Name PowerShellGet -Force
# Use Update-Module cmdlet to get the updated version
Update-Module -Name PowerShellGet
- Obtain the source
- Download the latest source code from the release page (https:/PowerShell/PowerShellGet/releases) OR
- Clone the repository (needs git)
git clone https://github.com/PowerShell/PowerShellGet
- Navigate to the source directory
cd path/to/PowerShellGet- Import the module
Import-Module /path/to/PowerShellGet/PowerShellGetPester-based PowerShellGet Tests are located in <branch>/PowerShellGet/Tests folder.
- Ensure Pester is installed on the machine
- Go the Tests folder in your local repository
- Run the tests by calling Invoke-Pester.
You are welcome to contribute to this project. There are many ways to contribute:
- Submit a bug report via Issues. For a guide to submitting good bug reports, please read Painless Bug Tracking.
- Verify fixes for bugs.
- Submit your fixes for a bug. Before submitting, please make sure you have:
- Performed code reviews of your own
- Updated the test cases if needed
- Run the test cases to ensure no feature breaks or test breaks
- Added the test cases for new code
- Submit a feature request.
- Help answer questions in the discussions list.
- Submit test cases.
- Tell others about the project.
- Tell the developers how much you appreciate the product!
You might also read these two blog posts about contributing code: Open Source Contribution Etiquette by Miguel de Icaza, and Don’t “Push” Your Pull Requests by Ilya Grigorik.
Before submitting a feature or substantial code contribution, please discuss it with the Windows PowerShell team via Issues, and ensure it follows the product roadmap. Note that all code submissions will be rigorously reviewed by the Windows PowerShell Team. Only those that meet a high bar for both quality and roadmap fit will be merged into the source.