Allow approval after a corrected submission passes its latest review - #44
Conversation
❌ Submission needs attention❌ 申请需要修改或人工处理
What to do next接下来怎么做For file or commit errors, fix them on the same branch used by this PR and commit/push the changes. The check will rerun automatically. Keep this PR open; you do not need a new one. If an error requires manual review, or you need help, leave a comment in this PR explaining the situation. A maintainer can review it or rerun the check; commenting alone does not clear the failed check. Human review contact: @maoawa. This is an automated result, not their approval. See the submission guide. Format checks do not assess website content or prove external domain ownership. Technical details / 技术详情Checked revision |
Editing a PR description creates another Actions check suite on the same commit. The approval service previously required every historical suite to pass, so an original missing-description failure blocked approval even after a successful recheck.
Resolve repeated Actions job names to their workflow identity and evaluate the newest run for that workflow/event/job. Keep unrelated workflows and apps as independent blockers, and reject incomplete or inconsistent check data. Approval errors now identify validation failures, mergeability, or the specific pending/failed check.
Validation: 35 Worker tests and the deployment dry run pass. Five regression tests cover superseded failures, new failures/pending runs, workflow/event/app isolation, mismatched metadata, and truncation. A read-only check using the production App confirms PR #42 passes validation and check readiness and is mergeable; no review or merge was performed.