Problem
The Jira ticket label remains forge:ci-pending after CI checks have passed on the associated PR. The workflow does not advance to forge:review-pending automatically. Manual intervention (forge:retry) is required to unstick it.
Observed on
Additional context
- A
/forge rebase was run on the PR before CI completed
gh pr checks reports "no checks reported" on the HEAD commit, while the PR status rollup shows passing checks — this suggests checks may be associated with a pre-rebase commit that is no longer HEAD- The workflow may not be matching CI results to the correct commit after a rebase
Expected Behavior
After CI passes on the PR, the workflow should advance from wait_for_ci_gate to ci_evaluator → human_review_gate, and the Jira label should update from forge:ci-pending to forge:review-pending.
Impact
Workflows silently stall at forge:ci-pending.
Problem
The Jira ticket label remains
forge:ci-pendingafter CI checks have passed on the associated PR. The workflow does not advance toforge:review-pendingautomatically. Manual intervention (forge:retry) is required to unstick it.Observed on
forge:ci-pendingwait_for_ci_gateAdditional context
/forge rebasewas run on the PR before CI completedgh pr checksreports "no checks reported" on the HEAD commit, while the PR status rollup shows passing checks — this suggests checks may be associated with a pre-rebase commit that is no longer HEADExpected Behavior
After CI passes on the PR, the workflow should advance from
wait_for_ci_gatetoci_evaluator→human_review_gate, and the Jira label should update fromforge:ci-pendingtoforge:review-pending.Impact
Workflows silently stall at
forge:ci-pending.