The GitHub Actions job "Release Auditing" on texera.git/ci/backport-out-of-required-checks has succeeded. Run started by GitHub user Yicong-Huang (triggered by Yicong-Huang).
Head commit for run: 0f6657fb9ae58d30dd6f479b536332a98839c0a0 / Yicong Huang <[email protected]> ci: move backport preflight out of Required Checks and report conflicts as neutral Backport preflight/build lived inside required-checks.yml, so a cherry-pick conflict surfaced as a failing `Required Checks / backport-apply-check (...)` job -- a red X that reads like a required check failed, though it is advisory (never in .asf.yaml's required set) and never blocks merge. - Extract precheck into a reusable workflow (precheck.yml) shared by the main build and the new backport preflight, so the label->stack mapping lives once. - Move backport apply-check + build into a dedicated Backport Checks workflow. apply-check is a single git-only job (no matrix, no backport-buildable aggregator) that never fails on a conflict; it writes the outcome to an artifact. - Add a Backport Preflight Publish workflow (workflow_run) that turns the artifact into a `backport-preflight (<target>)` check: success = clean, neutral (grey) = conflict. Never red, never a merge blocker. - Repoint Direct Backport Push to the neutral/success check (old apply-check job kept as a rollout fallback). - Auto-opened draft backport PRs: open as github-actions[bot], fill the PR template, drop the trailing "(#N)" link from the title, and carry the original PR's linked issues/discussion into the body. Report URL: https://github.com/apache/texera/actions/runs/30316328594 With regards, GitHub Actions via GitBox
