Document plugin maintenance branch policy in CONTRIBUTING.md - #340
Merged
Merged
Conversation
Clarifies that fork+PR into master-forge is the default path for every plugin update, and formalizes named per-plugin branches as a case-by-case exception for unresponsive maintainers, scoped to a single branch and always merged via PR (never a direct push) so CI still runs. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
master-forge, same as initial submission), and that write access/branches are not granted by default.geolayout-plugin) as a case-by-case exception for when a maintainer is unresponsive or their fork is gone, scoped to that one branch and always merged intomaster-forgevia PR — never a direct push, sincebuild.ymlskipsmaster-forgeentirely.Test plan
🤖 Generated with Claude Code