Skip to content

fix(required-gate): ignore unrelated label changes#58

Merged
ArchonVII merged 1 commit into
mainfrom
agent/codex/57-required-gate-label-triggers
Jun 9, 2026
Merged

fix(required-gate): ignore unrelated label changes#58
ArchonVII merged 1 commit into
mainfrom
agent/codex/57-required-gate-label-triggers

Conversation

@ArchonVII

Copy link
Copy Markdown
Owner

Summary

  • Remove broad labeled / unlabeled triggers from the required-gate caller example.
  • Document that ci:full is honored when the gate runs, but adding it after the latest run needs a rerun or normal PR event.
  • Add a regression assertion for the caller trigger shape.

Closes #57

Verification

  • npm test
  • actionlint examples/repo-required-gate.yml .github/workflows/repo-required-gate.yml
  • git diff --check

Verification Notes

npm test passed 6 files / 122 tests. actionlint returned no diagnostics for the changed caller example and reusable gate workflow. git diff --check returned no whitespace errors.

Remove broad labeled and unlabeled pull_request triggers from the required-gate caller example so labels like no-changelog do not restart the stable branch-protection gate. Document the ci:full rerun tradeoff and add a regression assertion.\n\nCloses #57
@ArchonVII
ArchonVII merged commit dc64da5 into main Jun 9, 2026
1 check passed
@ArchonVII
ArchonVII deleted the agent/codex/57-required-gate-label-triggers branch June 9, 2026 22:25

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7e721d88c5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +109 to +110
# If you add the label after the latest gate run, rerun the workflow,
# push a new commit, or use another normal PR event to refresh the gate.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Fetch current labels before suggesting reruns

When ci:full is added after the latest gate run and a maintainer follows this new instruction to rerun, the reusable workflow still builds labels from context.payload.pull_request in .github/workflows/repo-required-gate.yml, which is the original PR event payload rather than a fresh label lookup. GitHub re-runs use the original event's SHA/ref (docs), so the new label is not reliably present and the forced-full lane will not run; only a new PR event such as a push/edit refreshes it. Either fetch current issue labels during classification or remove rerun the workflow from this workaround.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ci: stop required gate from rerunning on arbitrary label changes

1 participant