kotkan/claude-plugin-inference-arbitrage
3
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

kotkan/claude-plugin-inference-arbitrage has no required-status-check branch protection, so merge_when_checks_succeed merges regardless of CI outcome #21

New Issue
Closed
opened 2026-07-30 05:51:49 +03:00 by issuer-agent · 1 comment
issuer-agent commented 2026-07-30 05:51:49 +03:00
Copy Link
Copy Source

Context: kotkan/claude-plugin-inference-arbitrage uses merge_when_checks_succeed as part of its CI-gated auto-merge convention (arm PR → watch CI → only proceed on green).

Observed failure: PR #18 was merged by merge_when_checks_succeed despite Woodpecker pipeline #4 failing on the suites step. The merge completed regardless of CI failure.

Root cause: No branch protection rule on kotkan/claude-plugin-inference-arbitrage requires the Woodpecker status check to pass before merge is allowed. This defeats the entire point of CI-gated auto-merge.

Why this matters: The grind workflow assumes CI gates the merge — a passing CI is the signal to proceed confidently. With no required-status-check, merge_when_checks_succeed is equivalent to an unconditional immediate merge.

Solutions:

  1. Add a branch protection rule on main requiring the Woodpecker check to pass before merge
  2. Audit other kotkan/* and oleks/* repos for the same gap (likely systemic)

Acceptance:

  • Branch protection rule enforces required Woodpecker status check on main
  • Verify PR merge is blocked when CI is red, proceeds only when CI is green
  • [Optional] Identify and file separate audit issue if this is systemic across kotkan/* and oleks/* repos
**Context**: kotkan/claude-plugin-inference-arbitrage uses merge_when_checks_succeed as part of its CI-gated auto-merge convention (arm PR → watch CI → only proceed on green). **Observed failure**: PR #18 was merged by merge_when_checks_succeed despite Woodpecker pipeline #4 failing on the suites step. The merge completed regardless of CI failure. **Root cause**: No branch protection rule on kotkan/claude-plugin-inference-arbitrage requires the Woodpecker status check to pass before merge is allowed. This defeats the entire point of CI-gated auto-merge. **Why this matters**: The grind workflow assumes CI gates the merge — a passing CI is the signal to proceed confidently. With no required-status-check, merge_when_checks_succeed is equivalent to an unconditional immediate merge. **Solutions**: 1. Add a branch protection rule on main requiring the Woodpecker check to pass before merge 2. Audit other kotkan/* and oleks/* repos for the same gap (likely systemic) **Acceptance**: - [ ] Branch protection rule enforces required Woodpecker status check on main - [ ] Verify PR merge is blocked when CI is red, proceeds only when CI is green - [ ] [Optional] Identify and file separate audit issue if this is systemic across kotkan/* and oleks/* repos
oleks commented 2026-07-30 15:49:21 +03:00
Owner
Copy Link
Copy Source

Branch Protection Configured

Added required-status-check branch protection to main that now blocks merge until Woodpecker CI passes.

Configuration:

  • Branch: main
  • Required Status Check: continuous-integration/woodpecker
  • Effect: PRs cannot be merged unless the Woodpecker status check passes

The standard Woodpecker status context continuous-integration/woodpecker is used by Woodpecker when reporting build status to Gitea. This ensures that CI pipeline failures (including the "suites" and "shellcheck" steps in .woodpecker/test.yaml) will block merge attempts rather than allowing unconditional immediate merge.

Verified: Branch protection rule is active and present via Gitea API.
Closes #21

## Branch Protection Configured Added required-status-check branch protection to `main` that now blocks merge until Woodpecker CI passes. **Configuration:** - **Branch:** main - **Required Status Check:** `continuous-integration/woodpecker` - **Effect:** PRs cannot be merged unless the Woodpecker status check passes The standard Woodpecker status context `continuous-integration/woodpecker` is used by Woodpecker when reporting build status to Gitea. This ensures that CI pipeline failures (including the "suites" and "shellcheck" steps in `.woodpecker/test.yaml`) will block merge attempts rather than allowing unconditional immediate merge. Verified: Branch protection rule is active and present via Gitea API. Closes #21
oleks closed this issue 2026-07-30 15:49:29 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
activity/automate
agent-wip
area/agent-behavior
Agent behavior and delegation logic
 bug
cost
domain/agents
Agent orchestration and multi-agent systems
 efficiency
infra-misconfig
kind/capability-gap
kind/defect
A defect or bug that needs fixing
 token-offload
A step paying for inference where a deterministic script would do (inference-arbitrage audit)
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
admin anton oleks
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kotkan/claude-plugin-inference-arbitrage#21
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?