agent/codex
1
0
Fork 0
mirror of https://github.com/pchuan98/codex.git synced 2026-07-01 00:31:56 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
9cd11e9e62c48ea6127f8b9f6ae2e013e4e4ff00
codex/.github/workflows
T
Michael Bolin 2375cb6449 ci: template custom runner names by repo (#27024) 
## Why

These workflows currently hard-code the `codex` runner group and custom
runner labels. That makes the same workflow definitions less portable
across repository copies or renamed repos, even though the runner fleet
follows the repository name scheme. Template the runner identities from
the repository name so `openai/codex` still resolves to the existing
`codex-*` runners while other repos can use their own `<repo>-*` runner
names.

## What Changed

- Replaced custom runner `group` values such as `codex-runners` with
`${{ github.event.repository.name }}-runners`.
- Replaced custom runner labels such as `codex-linux-x64` and
`codex-windows-arm64` with `${{ github.event.repository.name }}-...`.
- Covered direct `runs-on` objects, matrix `runs_on` entries, reusable
workflow runner inputs, and release runner labels.

## Verification

- Parsed all `.github/workflows/*.yml` files as YAML with Ruby.
- Searched `.github/workflows` to confirm no hardcoded runner-field
`codex-runners` or `codex-*` labels remain.
2375cb6449 ยท 2026-06-08 11:47:23 -07:00
History
..
bazel.yml
ci: template custom runner names by repo (#27024)
2026-06-08 11:47:23 -07:00
blob-size-policy.yml
ci: check out PR head commits in workflows (#21835)
2026-05-08 15:14:33 -07:00
cargo-deny.yml
[codex] Use git CLI for Cargo fetches across Rust workflows (#25775)
2026-06-02 07:39:41 -07:00
ci.yml
[codex] Add comprehensive root formatting check (#25683)
2026-06-02 01:20:25 +00:00
cla.yml
[codex] Pin GitHub Actions workflow references (#15828)
2026-03-27 23:00:05 +00:00
close-stale-contributor-prs.yml
[codex] Fully qualify hash-pins in GitHub Actions (#21436)
2026-05-07 14:31:20 -07:00
codespell.yml
ci: check out PR head commits in workflows (#21835)
2026-05-08 15:14:33 -07:00
Dockerfile.bazel
Remove js_repl feature (#19410)
2026-04-24 17:49:29 -07:00
issue-deduplicator.yml
ci: use issue triage environment for issue workflows (#25134)
2026-05-29 12:06:55 -07:00
issue-labeler.yml
ci: use issue triage environment for issue workflows (#25134)
2026-05-29 12:06:55 -07:00
python-runtime-build.yml
[codex] Split Python runtime release workflow (#26226)
2026-06-03 14:29:52 -07:00
python-runtime-release.yml
[codex] Split Python runtime release workflow (#26226)
2026-06-03 14:29:52 -07:00
python-sdk-release.yml
[codex] Split Python runtime release workflow (#26226)
2026-06-03 14:29:52 -07:00
README.md
Fan out rust-ci-full nextest by platform (#23358)
2026-05-19 17:54:41 -07:00
rust-ci-full-nextest-platform.yml
Uprev Rust toolchain pins to 1.95.0 (#24684)
2026-05-26 20:59:47 -07:00
rust-ci-full.yml
ci: template custom runner names by repo (#27024)
2026-06-08 11:47:23 -07:00
rust-ci.yml
ci: template custom runner names by repo (#27024)
2026-06-08 11:47:23 -07:00
rust-release-argument-comment-lint.yml
ci: template custom runner names by repo (#27024)
2026-06-08 11:47:23 -07:00
rust-release-prepare.yml
make rust-release-prepare use env secret (#22702)
2026-05-14 21:45:53 +00:00
rust-release-windows.yml
ci: template custom runner names by repo (#27024)
2026-06-08 11:47:23 -07:00
rust-release-zsh.yml
release: build macOS x64 zsh artifact (#24165)
2026-05-22 17:08:59 -07:00
rust-release.yml
ci: template custom runner names by repo (#27024)
2026-06-08 11:47:23 -07:00
rusty-v8-release.yml
ci: use bazel environment for BuildBuddy secret (#26895)
2026-06-07 09:24:54 -07:00
sdk.yml
ci: template custom runner names by repo (#27024)
2026-06-08 11:47:23 -07:00
v8-canary.yml
ci: use bazel environment for BuildBuddy secret (#26895)
2026-06-07 09:24:54 -07:00
zstd
ci(windows): use DotSlash for zstd in rust-release-windows (#11542)
2026-02-11 20:57:11 -08:00

README.md

Workflow Strategy

The workflows in this directory are split so that pull requests get fast, review-friendly signal while main still gets the full cross-platform verification pass.

Pull Requests

  • bazel.yml is the main pre-merge verification path for Rust code. It runs Bazel test and Bazel clippy on the supported Bazel targets, including the generated Rust test binaries needed to lint inline #[cfg(test)] code.
  • rust-ci.yml keeps the Cargo-native PR checks intentionally small:
    • cargo fmt --check
    • cargo shear
    • argument-comment-lint on Linux, macOS, and Windows
    • tools/argument-comment-lint package tests when the lint or its workflow wiring changes

Post-Merge On main

  • bazel.yml also runs on pushes to main. This re-verifies the merged Bazel path and helps keep the BuildBuddy caches warm.
  • rust-ci-full.yml is the full Cargo-native verification workflow. It keeps the heavier checks off the PR path while still validating them after merge:
    • the full Cargo clippy matrix
    • the full Cargo nextest matrix via per-platform archive-backed shards
    • Windows ARM64 nextest archives cross-compiled on Windows x64, then replayed on native Windows ARM64 shards
    • release-profile Cargo builds
    • cross-platform argument-comment-lint
    • Linux remote-env tests

Rule Of Thumb

  • If a build/test/clippy check can be expressed in Bazel, prefer putting the PR-time version in bazel.yml.
  • Keep rust-ci.yml fast enough that it usually does not dominate PR latency.
  • Reserve rust-ci-full.yml for heavyweight Cargo-native coverage that Bazel does not replace yet.
Reference in New Issue View Git Blame Copy Permalink