Skip to content

ci: Relabel pull requests on every edit #265

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
RobinBol merged 1 commit into from
Oct 28, 2026
Merged

ci: Relabel pull requests on every edit #265

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .github/workflows/label-pr.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name: Label pull request

# Labels each pull request from the conventional-commit prefix of its title, so the release
# notes can sort it (see .github/release.yml). Re-runs when the title or base branch is edited.
# notes can sort it (see .github/release.yml). Re-runs on every edit.
# The five labels below follow the title alone: to move a pull request, retitle it.
#
# pull_request_target so pull requests from forks get a token that can label. This is safe
Expand Down Expand Up @@ -40,9 +40,9 @@ jobs:
return null;
}

const { action, changes = {} } = context.payload;
// The label depends on the title and the base branch; other edits change nothing.
if (action === 'edited' && !changes.title && !changes.base) return;
// No early return for edits that leave the title and base alone: a newer queued run in
// the concurrency group replaces an older one, so a body edit can be all that runs
// after a title edit.

// The payload is a snapshot from when the event fired. Read the pull request as it is
// now, so labels an earlier run added are seen and the latest title wins.
Expand Down
Loading