Thanks for your interest in contributing to Pact Community projects. This is the
organization-wide baseline; individual repositories may add their own
CONTRIBUTING.md with project-specific build and test instructions.
- Questions / ideas: open a Discussion first.
- Bugs: open an issue with the Bug Report template (clear repro steps).
- Features / RFCs: open a Feature Request issue or Discussion. For anything large, please discuss before writing code — an accepted issue is not guaranteed, and unsolicited large PRs may not be merged.
- Security: never open a public issue — see SECURITY.md.
- Be respectful — see the Code of Conduct.
- Keep changes focused and minimal; one logical change per PR.
- Discuss design before large refactors.
- Do not include secrets, credentials, or private keys in code, tests, or issues.
- By contributing, you agree your contributions are licensed under the repository's license.
- Fork and create a branch:
feature/<short-description>orbugfix/<short-description>. - Follow the repository's coding and test conventions.
- Use Conventional Commits for commit messages.
- Ensure tests and CI pass locally where possible.
- Open the PR using the repository's PR template and fill it out completely.
- Respond to review feedback; keep the PR up to date with
main.
These are community, best-effort projects. Maintainers triage as capacity allows. Thoughtful, well-scoped, well-tested contributions are reviewed fastest. Thank you for helping improve the Pact ecosystem.