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
- ..
- about.rs
- backups.rs
- blame.rs
- catch_up.rs
- coalesce.rs
- commit_file.rs
- contributors.rs
- diff.rs
- drift.rs
- fallback.rs
- forks.rs
- git_http.rs
- git_ops.rs
- import.rs
- land.rs
- languages.rs
- last_commits.rs
- lib.rs
- license.rs
- lifecycle.rs
- limits.rs
- listing.rs
- meters.rs
- mirror.rs
- moves.rs
- namespaces.rs
- pack_cache.rs
- pack_limits.rs
- push_checks.rs
- push_commits.rs
- refs.rs
- refs_cache.rs
- registry.rs
- resilience.rs
- rule_facts.rs
- rules.rs
- run_access.rs
- secret_scan.rs
- shards.rs
- shared.rs
- signatures.rs
- stats.rs
- store.rs
- transfer.rs
- workflow_gate.rs