chore(repo): adopt Markpad labels and retire unused defaults - #135
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
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 ten-label Markpad baseline and preserve project-specific labels. Remove unused default labels from the manifest and record explicit cleanup separately from additive synchronization.
Keep
Final_Check_Requestas a manual marker; completed work can still use closing keywords without a release-confirmation bot.Verification
JSON/YAML, script syntax and manifest checks passed. Explicit source-manifest preview stayed read-only. All five retired labels had zero usage across open and closed issues/PRs before removal. Remote labels and settings are read back against the manifests. No application code changed.
Baseline
Merge PathGao/PathGao#2 first. The adopted source snapshot is recorded in the governance guide.