Skip to content

Move backport preflight/build out of Required Checks and report conflicts as neutral #6954

Description

@Yicong-Huang

Task Summary

Two follow-ups to the #6941 backport automation, both about the backport CI/PRs being confusing or noisy.

1. Move backport preflight out of Required Checks; conflicts render neutral, not red. Backport preflight lives inside required-checks.yml and reports a cherry-pick conflict as a failing job (Required Checks / backport-apply-check (…)) — a red X that reads like a required check failed, even though it is advisory (not in .asf.yaml) and never blocks merge (e.g. #6909). Extract the backport jobs into a dedicated Backport Checks workflow (sharing precheck via a reusable workflow), and report per-target results as neutral (grey) via a workflow_run companion: success = cherry-picks cleanly, neutral = conflicts.

2. Improve the auto-opened draft backport PRs. (a) Open them as github-actions[bot] (GITHUB_TOKEN) instead of the PAT owner; (b) fill the repo PR template in the body; (c) strip the trailing (#N) from the title so it does not render as a link back to the original PR.

Merge-gating is unchanged — backport was never a required context.

Task Type

  • Refactor / Cleanup
  • DevOps / Deployment / CI
  • Testing / QA
  • Documentation
  • Performance
  • Other

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions