Community and contributing

Canonical policies

The repository's Code of Conduct defines respectful participation, reporting, moderation, and reconsideration. The Contributing Guidelines describe isolated development, full validation, security review, versioning, documentation, and rollback. These files are the authoritative policies; this website does not maintain competing copies.

Choose a report

Use the GitHub issue chooser for a reproducible bug, a feature proposal, or a documentation correction. A useful bug report includes the exact version, environment, reproduction steps, expected behavior, and actual behavior. Feature requests explain the problem, alternatives, and acceptance criteria. Documentation reports identify the page and proposed correction.

Keep private information private

Public reports must not contain passwords, access tokens, authorization headers, private task data, databases, or unredacted settings and screenshots. Security vulnerabilities follow SECURITY.md. Behavior concerns use the Code of Conduct's reporting routes, not a public issue containing incident details.

Prepare a pull request

The pull request template asks for scope, issue references, change classification, version/changelog details, actual test results, security and compatibility review, documentation, release artifacts, rollback, and copyable commit notes. Mark unperformed checks honestly. Maintainers review changes before merging.

Template availability

GitHub offers issue forms and the default pull request template after their files reach the default branch. Passing repository tests verifies the checked-in structure and links, not a live GitHub form submission. Source release publication and deployment of an existing application remain separate steps.