chore: align repository governance - #134
Merged
Merged
Conversation
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
Adopt the PathGao governance baseline with a short PR template, shared label meanings and reviewable GitHub settings. Completed issues close on merge with
ClosesorFixes.Preserve site forms and existing CI protection. Replace the label manifest/parser with JSON and correct release-signing guidance. Historical labels remain intact.
Verification
JSON/YAML, form-label references, template consistency and shell checks passed. Seven isolated label-sync cases passed. GitHub settings and rulesets match their manifests; live label preview reports zero differences. No app code changed. Actual PR/merge behavior remains to be checked after publication.
Baseline
Merge PathGao/PathGao#1 first to publish the shared baseline.