docs: document PR base-branch pitfall for forked template projects - #111
Merged
Conversation
Downstream forks of peerigon/template default new PRs to the upstream repo, which fails fork-specific checks like CODEOWNERS and rulesets.
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.
Summary
peerigon/templatedefault new PRs to the upstream repo (viaghor the GitHub web UI), which breaks fork-specific checks like CODEOWNERS and rulesets.gh repo set-default <owner>/<repo>once per clone, or pass--repo <owner>/<repo>explicitly.Adapted from peerigon/leitstand#34bc583, generalized since this repo is the template itself rather than a fork.
Test plan