Skip to content

refactor\(source-control\)!: remove resolve-conflicts in favour of the pull-request conflict mode - part 2 of 3 #13198

Description

@melodic-automation-lanes

Part 2 of 3 of #13138, split at intake (owner Q93). The done-when below is copied from #13138 as written.

Done when

  • The resolve-conflicts activity's skill: and args: in docs/conventions/pr-pipeline.yaml:35-36 and docs/conventions/pr-pipeline/examples/claude-code-plugins.yaml:74 name the PR 2 skill and mode, with --unattended in args (docs/conventions/pr-pipeline.yaml:93-94), and the activity keeps its name resolve-conflicts. .github/actions/collect-base-activity/collect-base-activity.test.mjs, .github/actions/resolve-config/feedback-dispatch.test.mjs and .github/actions/resolve-config/live-config.test.mjs assert the new skill and allowed-tools grant.

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 4, 2026
  2. github-actions commented on Nov 4, 2026

    @github-actions
    Contributor

    Proposed work class: work-class: scoped
    Basis: automated intake triage; the lanes App applied this class.

    Size: Small
    Complexity: Low
    Uncertainty: Known
    Flags: none
    Blocked by: #13197

    Understood: this is part 2 of 3 of #13138. It repoints the resolve-conflicts activity's skill: and args: (with --unattended) in the pipeline config and example to the new pull-request conflict mode. It also updates three test files to assert the new skill and allowed-tools grant. The activity keeps its name.

    It depends on part 1 (#13197), which should provide the skill and mode this part names. Part 3 is #13199. These are sibling split children, not duplicates.

    Automated triage, applied by the lanes App.

  3. added
    priority: mediumReal value, no hard deadline; normal backlog flow.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 4, 2026
  4. melodic-automation-lanes commented on Nov 4, 2026

    @melodic-automation-lanes
    ContributorAuthor

    The latest triage verdict holds nothing: the issue is at status: ready.

  5. melodic-automation-lanes commented on Nov 4, 2026

    @melodic-automation-lanes
    ContributorAuthor

    Not admitted to the issue lane yet: blocker #13197 is not closed by a listed human or a merge.

  6. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 4, 2026
  7. github-actions commented on Nov 4, 2026

    @github-actions
    Contributor
    No description provided.
  8. github-actions commented on Nov 4, 2026

    @github-actions
    Contributor
    No description provided.
  9. removed
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 4, 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

    priority: mediumReal value, no hard deadline; normal backlog flow.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Type

    Fields

    Work status

    agent-ready

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions