Repository navigation
Add an organisation wide pull request template - #1
Merged
Merged
Conversation
GitHub serves default community health files from this repo to every repository in the organisation that does not have its own, so this needs writing once instead of being copied into each package. The template asks two things: what the change does, and whether an AI assistant wrote a meaningful part of it. The second question is routing information for the reviewer, not a gate. The policy behind it lives in each repository's CONTRIBUTING.md, starting with zostera/django-marina#679. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This was referenced Sep 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This repo already serves
FUNDING.ymlto the whole organisation. It can serve a pull request template the same way: GitHub applies default community health files fromzostera/.githubto every repository that does not carry its own, so this is written once rather than copied into five packages and every future repo.The template asks what the change does and whether an AI assistant wrote a meaningful part of it. The second question is routing information for whoever reviews, not a gate, and either answer is fine. The policy it refers to lives in each repository's
CONTRIBUTING.mdand starts with zostera/django-marina#679, which is where the shared version is maintained.Worth knowing about the limits of this mechanism: defaults apply only where a repo has no file of its own. That works for the PR template, since none of the five packages has one. It will not work for
CONTRIBUTING.md, because all five have their own and each needs its own scope section, which is why the policy text is copied per repo rather than centralised here.A
SECURITY.mdwould be the next obvious file to add here, since none of the five packages has one. Left out of this PR deliberately, as it needs a real decision about how reports are received rather than a template.🤖 Generated with Claude Code