Make release.yml the PR-label source of truth; label PRs at creation - #480
Merged
ChrisonSimtian merged 1 commit intoJul 12, 2026
Merged
Conversation
…t creation Contributors weren't consistently labelling PRs, so release notes fell through to 'Other Changes'. - .github/release.yml: document the label taxonomy inline (header + per-label blurbs on what each is for). It already drives auto-generated release notes; now it's also the canonical reference for which label to apply. - issue-and-pr-style.md: add a label-at-creation rule next to the raise-in-draft rule. - release-and-versioning.md: add a changelog-category-label step to the PR-creation flow. - AGENTS.md: rule #1 now names the category label + points at release.yml. So AI applies the matching changelog-category label whenever it raises a PR on the user's behalf. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ChrisonSimtian
added
documentation
Contributor
|
@ChrisonSimtian If you are not using any AI agent.. does not help in that case, does it? |
ChrisonSimtian
marked this pull request as ready for review
July 12, 2026 05:24
Collaborator
Author
@IT-VBFK nope it doesnt, unless you read through the Agent.md :D But I reckon most PRs will be AI generated to some degree and at least those ones will be covered. The rest we'll just have to go through manually |
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.
Contributors weren't consistently labelling PRs, so release notes kept falling through to "Other Changes". Makes
.github/release.ymlthe single source of truth for the label taxonomy and requires labelling at PR-creation.What
.github/release.yml— documents the taxonomy inline (header + a one-line blurb per label on what it's for). It already drives auto-generated release notes; now it's also the canonical reference for which label to apply. No behavior change (comments only).issue-and-pr-style.md— label-at-creation rule added next to the existing raise-in-draft rule.release-and-versioning.md— a changelog-category-label step added to the PR-creation flow.AGENTS.md— rule Security: pin vulnerable transitives (CVE-2026-33116, Scriban) — mirrors upstream #1592 #1 now names the category label and points atrelease.yml.Net: AI applies the matching changelog-category label (
enhancement/bug/security/documentation/breaking-change/skip-changelog) whenever it raises a PR on the user's behalf.Verification
release.ymlre-parses (categories + excludes unchanged); relative doc links resolve. This PR is labelled per the new rule (documentation+target/2026).🤖 Generated with Claude Code