Skip to content

ci: tolerate conflict comment permission failures#7333

Draft
thepastaclaw wants to merge 2 commits into
dashpay:v23.1.xfrom
thepastaclaw:ci/v23-predict-conflicts-permissions
Draft

ci: tolerate conflict comment permission failures#7333
thepastaclaw wants to merge 2 commits into
dashpay:v23.1.xfrom
thepastaclaw:ci/v23-predict-conflicts-permissions

Conversation

@thepastaclaw
Copy link
Copy Markdown

Backport predict-conflicts comment hardening

Summary

  • Update the conflict-prediction PR comment action from
    mshick/add-pr-comment@v2 to @v3.
  • Make both conflict-comment maintenance steps non-fatal with
    continue-on-error: true.
  • Keep the actual conflict detector/final failure step authoritative, so real
    predicted conflicts still fail CI.

Context

dashpay/dash#7321 is approved and mergeable, but the predict_conflicts
workflow is red because comment maintenance failed with
Resource not accessible by integration. This backport keeps comment posting or
removal from failing the workflow when the detector itself succeeded.

Validation

  • git diff --check upstream/v23.1.x...HEAD
  • Parsed .github/workflows/predict-conflicts.yml as YAML.
  • Pre-PR code review:
    code-review dashpay/dash upstream/v23.1.x ci/v23-predict-conflicts-permissions
    → Recommendation: ship.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 20, 2026

✅ No Merge Conflicts Detected

This PR currently has no conflicts with other open PRs.

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