Claudeagent and ClaudeagentA required check named for a workflow job, as GitHub's branch rules name them, is met by that job. Each g1t Actions job on a pull request's head counts as a check of its name (`test`, `build (ubuntu-latest, 22)`, or `deploy / build` for a called workflow's job), from the latest attempt of its workflow: skipped passes, cancelled fails, and a job still going holds the merge. So a ruleset or required check copied from GitHub needs no renaming, and one that names the workflow, such as `CI`, is met by the whole run as before. This holds in the merge box, for the merge queue and for agents' merges; jobs count only toward required checks, so a `continue-on-error` job that fails doesn't send an agent back. The pull requests guide says so.d4e4a46History
- ..
- agent_comments.rs
- authored.rs
- capture.rs
- checks.rs
- codeowners.rs
- commit_checks.rs
- compute.rs
- confidence.rs
- contributions.rs
- ghost.rs
- guardrails.rs
- inbox.rs
- labels.rs
- lib.rs
- lifecycle.rs
- memory.rs
- mentions.rs
- mergeability.rs
- messages.rs
- milestones.rs
- plans.rs
- prefetch.rs
- queue.rs
- retired.rs
- reviews.rs
- rows.rs
- rulesets.rs
- runs.rs
- settings.rs
- statuses.rs
- team_reviews.rs