Create your own copy of the project by clicking the "Fork" button at the top right of the repository page.
Download your fork to your local machine:
git clone https://github.com/OWNER/PSModuleTemplate.git
cd PSModuleTemplateMake a new branch for your changes (don't work directly on main/master):
git checkout -b your-branch-nameUse a descriptive branch name like fix-bug-123 or add-feature-xyz.
Edit code, add features, fix bugs, or improve documentation as needed.
Before committing, ensure your changes work correctly:
make setupThis will set up an example module for testing.
make dependThis installs any required modules defined in PSDepend.psd1. If your changes add a new module dependency, make sure it is listed in both PSDepend.psd1 and in RequiredModules in the module manifest.
make buildReview the build output to ensure there are no errors.
make pesterAll tests should pass before submitting your pull request.
- If you modify Pester tests: Create example functions and ensure to reference GitHub Actions runs on your forked repository
- If you modify scripts or workflows: Verify that the associated pipelines run correctly in your fork
- If you add dependencies: Ensure they are declared in both
PSDepend.psd1andRequiredModulesin the module manifest
Save your work with clear, descriptive commit messages:
git add .
git commit -m "Brief description of your changes"Upload your branch to your GitHub fork:
git push origin your-branch-nameGo to the original repository on GitHub and click "New Pull Request". Select your fork and branch, then provide a clear description of your changes.
- Write clear commit messages
- Follow the existing code style
- Test your changes before submitting
- Update documentation if needed
- Be respectful and constructive in discussions
If you have questions or need help, feel free to open an issue.
Thank you for contributing!