Claude/generate skill documentation f npo6 - #5
Merged
Conversation
- .github/CODEOWNERS routes review on every PR. - .github/workflows/release-guard.yml rejects PRs into release that don't come from main, and rejects direct pushes whose tip isn't an ancestor of origin/main. - .github/pull_request_template.md flags whether a PR targets release. These are git-side guards; pair with the GitHub branch protection rule for full enforcement (instructions in README).
- release is the integration/daily-release branch; accepts PRs from any branch. - main is the stable publish branch; only accepts PRs from release. - release-guard workflow renamed to branch-policy with four jobs covering push and PR events on both protected branches. - READMEs (zh/en) and PR template updated to reflect the new flow and document the one-time gh api calls needed to enable UI-level branch protection.
- CHANGELOG.md following Keep a Changelog / SemVer - .github/RELEASE_NOTES_v1.0.0.md as the body for the GitHub Release
4 tasks
Gutiz
added a commit
that referenced
this pull request
May 29, 2026
… notes) (#7) * Claude/generate skill documentation f npo6 (#5) * Add lightweight release-branch guard (CODEOWNERS + Actions) - .github/CODEOWNERS routes review on every PR. - .github/workflows/release-guard.yml rejects PRs into release that don't come from main, and rejects direct pushes whose tip isn't an ancestor of origin/main. - .github/pull_request_template.md flags whether a PR targets release. These are git-side guards; pair with the GitHub branch protection rule for full enforcement (instructions in README). * Switch branch policy: feature -> release -> main - release is the integration/daily-release branch; accepts PRs from any branch. - main is the stable publish branch; only accepts PRs from release. - release-guard workflow renamed to branch-policy with four jobs covering push and PR events on both protected branches. - READMEs (zh/en) and PR template updated to reflect the new flow and document the one-time gh api calls needed to enable UI-level branch protection. * Prepare v1.0.0 release notes and changelog - CHANGELOG.md following Keep a Changelog / SemVer - .github/RELEASE_NOTES_v1.0.0.md as the body for the GitHub Release --------- Co-authored-by: Claude <noreply@anthropic.com> * Codex/release update f npo6 (#6) * Add lightweight release-branch guard (CODEOWNERS + Actions) - .github/CODEOWNERS routes review on every PR. - .github/workflows/release-guard.yml rejects PRs into release that don't come from main, and rejects direct pushes whose tip isn't an ancestor of origin/main. - .github/pull_request_template.md flags whether a PR targets release. These are git-side guards; pair with the GitHub branch protection rule for full enforcement (instructions in README). * Switch branch policy: feature -> release -> main - release is the integration/daily-release branch; accepts PRs from any branch. - main is the stable publish branch; only accepts PRs from release. - release-guard workflow renamed to branch-policy with four jobs covering push and PR events on both protected branches. - READMEs (zh/en) and PR template updated to reflect the new flow and document the one-time gh api calls needed to enable UI-level branch protection. * Prepare v1.0.0 release notes and changelog - CHANGELOG.md following Keep a Changelog / SemVer - .github/RELEASE_NOTES_v1.0.0.md as the body for the GitHub Release --------- Co-authored-by: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <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
2 participants
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.
No description provided.