Thank you for your interest in contributing to Pepr! We welcome all contributions and are grateful for your help. This guide outlines how to get started with contributing to this project.
Please follow our Code of Conduct to maintain a respectful and collaborative environment.
- Repository: https://github.com/defenseunicorns/pepr/
- npm package: https://www.npmjs.com/package/pepr
- Required Node version:
>=18.0.0
- Fork the repository.
- Clone your fork locally:
git clone https://github.com/your-username/pepr.git
. - Install dependencies:
npm ci
. - Create a new branch for your feature or fix:
git checkout -b my-feature-branch
.
- Create an Issue: For significant changes, please create an issue first, describing the problem or feature proposal. Trivial fixes do not require an issue.
- Commit Your Changes: Make your changes and commit them. All commits must be signed.
- Run Tests: Ensure that your changes pass all tests by running
npm test
. - Push Your Branch: Push your branch to your fork on GitHub.
- Create a Pull Request: Open a pull request against the
main
branch of the Pepr repository. Please make sure that your PR passes all CI checks.
- PRs must be against the
main
branch. - PRs must pass CI checks.
- All commits must be signed.
- PRs should have a related issue, except for trivial fixes.
Please follow the coding conventions and style used in the project. Use ESLint and Prettier for linting and formatting:
- Check formatting:
npm run format:check
- Fix formatting:
npm run format:fix
- Run all tests:
npm test
- Run
npm test
and wait for completion. - Change to the test module directory:
cd pepr-test-module
. - You can now run any of the
npx pepr
commands.
For any questions or concerns, please open an issue on GitHub or contact the maintainers.