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
- ..
- folios
- kinds
- access.test.ts
- access.ts
- blocks.ts
- chunks.test.ts
- chunks.ts
- citations.test.ts
- citations.ts
- diff.test.ts
- diff.ts
- edits.test.ts
- edits.ts
- events.ts
- files.test.ts
- files.ts
- folio-access.test.ts
- index.ts
- indexer.test.ts
- indexer.ts
- markdown.test.ts
- markdown.ts
- persist.ts
- recall.test.ts
- recall.ts
- repo-docs.test.ts
- repo-docs.ts
- repo-spaces.ts
- room.ts
- search.test.ts
- search.ts
- sigv4.test.ts
- sigv4.ts
- slugs.test.ts
- slugs.ts
- staleness.ts
- templates.ts
- threads.test.ts
- threads.ts
- tree.test.ts
- tree.ts
- vectors.ts
- who.ts