Skip to content

docs(pr-pipeline): hold a lane PR on a not-verified item that can stop the lane - #7888

Merged
kyle-sexton merged 5 commits into
mainfrom
docs/7886-lane-unverified-item-rule
Oct 18, 2026
Merged

kyle-sexton merged 5 commits into
mainfrom
docs/7886-lane-unverified-item-rule

Conversation

@kyle-sexton

@kyle-sexton kyle-sexton commented Oct 18, 2026 •

Copy link
Copy Markdown
Member

Refs: #7886

Summary

melodic-software/ci-workflows#755 changed the intake lane and listed its author gate as "unverified, fails closed" in the PR body. It merged unchecked, failed closed, and every intake run here skipped triage behind a green check (melodic-software/ci-workflows#772). The check was cheap before merge: an anonymous API read of any issue shows the CONTRIBUTOR association the webhook sends.

Fix

One rule under Changing this config: a PR that changes a lane and lists a not-verified item that could stop the lane from running checks that item live before it merges. An item only a merged run can exercise, such as a changed workflow that runs from the base branch, merges only once a tracked issue names the check and its owner. A PR-body line does not count. The incident is cited as the observed-stumble evidence. CHANGELOG 2.11.0.

Verification

  • markdownlint-cli2 on both files: 0 issues.
  • scripts/check-affected.sh --tests: 6 passed, 3 skipped.
  • Left out: nothing else applies (docs only).

Related

🤖 Generated with Claude Code

https://claude.ai/code/session_019bQ8pL7fJgVy7YjQ7wK1Zw

…p the lane

ci-workflows#755 shipped an intake author gate it listed as "unverified,
fails closed"; it failed closed and skipped every intake run. A lane PR
with such an item now waits for a live check, and the post-merge live
check is a tracked issue rather than a PR-body line.

Refs: #7886

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019bQ8pL7fJgVy7YjQ7wK1Zw
@kyle-sexton
kyle-sexton marked this pull request as ready for review October 18, 2026 02:52
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 18, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-18T02:53:19.539792Z bf83885 Draft marked ready
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@github-actions

github-actions Bot commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

claude-security-review needs no new review of 4e1ef0dc03c92f31d7689e5710e634c74323c413: every file in scope matches docs-only-paths.

Comment thread docs/conventions/pr-pipeline/README.md Outdated
@github-actions

github-actions Bot commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

claude-review reviewed 4e1ef0dc03c92f31d7689e5710e634c74323c413: 0 finding(s), 0 as inline comments.

No findings. I reviewed the two-file docs change, which adds a rule under "Changing this config" in the pr-pipeline README and a 2.11.0 CHANGELOG entry.

  • Rule and entry: the README rule and the CHANGELOG entry say the same thing. The rule cites the ci-workflows#755 and chore(deps): bump brace-expansion from 5.0.6 to 5.0.7 in /plugins/ai-briefing/skills/generate/output/build #772 incident as its observed-stumble evidence, as the repository's instruction-economy rule asks.
  • Version: 2.11.0 follows 2.10.0 with the same date. I found no other place in docs/conventions/pr-pipeline that states a version number, so there is nothing else to bump.
  • Line length: one added README line runs past the wrap width used nearby. MD013 is disabled in .markdownlint-cli2.jsonc, so it cannot fail lint, and I did not flag it.
  • Closing issue: the PR uses Refs: #7886, so there is no closing issue and no acceptance criteria to check.
  • Not verified: I did not run markdownlint-cli2 or scripts/check-affected.sh. The results in the PR body are the author's claims.

@melodic-automation-lanes melodic-automation-lanes Bot added the needs-human Human-in-the-loop required; autonomous sessions must not resolve items carrying this. label Oct 18, 2026
@melodic-automation-lanes

Copy link
Copy Markdown
Contributor

The pr-unblock lane stopped on this pull request and needs a person: the merge stages a change under .github/workflows/, which the lane does not push.

  • Reason: workflow-staged
  • Resume key: bf838852cef08f651c038a3c3a4640aa70b478a3 (the head the lane stopped on)

To resume, deal with the reason above, remove the needs-human label (and do-not-merge, if set), then dispatch the pr-unblock workflow with pr-number=7888 and activity=resolve-conflicts:

gh workflow run pr-unblock.yml -R melodic-software/claude-code-plugins -f pr-number=7888 -f activity=resolve-conflicts

Resolves the pr-pipeline CHANGELOG conflict by moving this entry to 2.10.0 above main's 2.9.1. Also rewords the rule so it no longer contradicts itself: check the item live before merging, and when only a merged run can exercise it, merge once a tracked issue names the check and its owner.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kyle-sexton kyle-sexton removed the needs-human Human-in-the-loop required; autonomous sessions must not resolve items carrying this. label Oct 18, 2026
Comment thread docs/conventions/pr-pipeline/CHANGELOG.md Outdated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@melodic-automation-lanes melodic-automation-lanes Bot added the needs-human Human-in-the-loop required; autonomous sessions must not resolve items carrying this. label Oct 18, 2026
@melodic-automation-lanes

Copy link
Copy Markdown
Contributor

The pr-unblock lane stopped on this pull request and needs a person: the merge stages a change under .github/workflows/, which the lane does not push.

  • Reason: workflow-staged
  • Resume key: 8126d7a9fc44bf11db4cff34ff3c62400f7576eb (the head the lane stopped on)

To resume, deal with the reason above, remove the needs-human label (and do-not-merge, if set), then dispatch the pr-unblock workflow with pr-number=7888 and activity=resolve-conflicts:

gh workflow run pr-unblock.yml -R melodic-software/claude-code-plugins -f pr-number=7888 -f activity=resolve-conflicts

Main took pr-pipeline 2.10.0, so this entry moves to 2.11.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kyle-sexton kyle-sexton removed the needs-human Human-in-the-loop required; autonomous sessions must not resolve items carrying this. label Oct 18, 2026
@kyle-sexton
kyle-sexton added this pull request to the merge queue Oct 18, 2026
Merged via the queue into main with commit f2e4dfb Oct 18, 2026
69 of 71 checks passed
@kyle-sexton
kyle-sexton deleted the docs/7886-lane-unverified-item-rule branch October 18, 2026 05:23
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.

1 participant