Skip to content

fix(pr-pipeline): re-trigger PR lane checks refused as workflow-modified #7849

Closed

Description

@kyle-sexton

Problem

A PR lane check whose workflow file changed on main after the run's event can't be cleared by a rerun: the broker refuses the rerun as workflow-modified, as in pr-merge run https://github.com/melodic-software/claude-code-plugins/actions/runs/39072924587. Today a person or session has to update the branch to get a new head. #7828 fixed this for issue-lane runs (work-unblock re-fires agent-ready); PR-side lanes (pr-merge, pr-refine, pr-unblock) have no equivalent. Workflow files changed on main several times on 2026-10-17, so this hit many PRs at once.

Proposed fix

When a PR-side lane run fails at "Request the lane token" with workflow-modified, start a fresh event for that PR through the existing App path, with the same once-per-workflow-version bound as #7828. Updating the branch through the lanes App is the likely smallest event.

Acceptance criteria

  • A PR whose lane check failed with workflow-modified gets a fresh run within one sweep, with no person involved.
  • It never loops for the same workflow blob.

Refs: #7816, #7828

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageNot yet classified. Floor until a type and one priority tier are set.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions