Skip to content

fix: autolabel scoped conventional commit titles#455

Open
ssbarnea wants to merge 1 commit intomainfrom
fix/autolabeler-scoped-conventional-commits
Open

fix: autolabel scoped conventional commit titles#455
ssbarnea wants to merge 1 commit intomainfrom
fix/autolabeler-scoped-conventional-commits

Conversation

@ssbarnea
Copy link
Copy Markdown
Member

Problem

Many open PRs on ansible-automation-platform/ansible-devtools-container fail the shared ack workflow (ansible/team-devtools/.github/workflows/ack.yml) with:

Label error. Requires at least 1 of: breaking, chore, feat, fix. Found: .

Example failed job log (PR 1052): release-drafter/autolabeler runs, then github-action-required-labels finds no matching label.

Mintmaker and similar bots open titles like chore(deps): update …. The autolabeler only matched chore: (no scope), so chore(deps): never received the chore label.

Change

  • Allow optional conventional-commit (scope) before : for feat, fix, and chore|build|ci|test|style.
  • Restore optional leading […] backport-style prefixes for those types (and breaking) so patchback titles still autolabel.

After merge

Re-run or push an empty commit on affected ansible-devtools-container PRs so pull_request_target picks up the updated _extends config from main (no container repo change required for ack).

Konflux

Several PRs also show Konflux / Conforma failures; those need triage in Konflux UI (not visible from public CI logs here); fixing ack unblocks the GitHub-side gate only.

Release-drafter autolabeler required type prefixes immediately
followed by a colon, so titles like chore(deps): from Mintmaker
never received the chore label and the shared ack workflow failed
required-label checks.

Restore optional backport-style [tag] prefixes for feat/fix/chore
and allow an optional (scope) before the colon. Align breaking
detection with the same bracket prefix pattern.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant