polymech/zeroclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
c1e1228fb0
zeroclaw/.github/workflows
History
simianastronaut c1e1228fb0 ci: use thin LTO profile for faster CI builds 
The release profile uses fat LTO + codegen-units=1, which is
optimal for distribution binaries but unnecessarily slow for CI
validation builds. Add a dedicated `ci` profile with thin LTO and
codegen-units=16, and use it in both CI workflows.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-12 17:18:36 -04:00
..
checks-on-pr.yml ci: use thin LTO profile for faster CI builds 2026-03-12 17:18:36 -04:00
ci-run.yml ci: use thin LTO profile for faster CI builds 2026-03-12 17:18:36 -04:00
cross-platform-build-manual.yml chore(deps): bump actions/download-artifact from 4 to 8 2026-03-11 04:30:08 -04:00
master-branch-flow.md chore(github): update review ownership routing (#3216) 2026-03-11 19:11:53 -04:00
README.md chore: update .gitignore, CODEOWNERS, and dependabot configuration 2026-03-07 21:05:23 -05:00
release-beta-on-push.yml fix(release): lower GNU Linux build runner baseline (#3257) 2026-03-11 23:43:14 -04:00
release-stable-manual.yml fix(release): lower GNU Linux build runner baseline (#3257) 2026-03-11 23:43:14 -04:00

README.md

Workflow Directory Layout

GitHub Actions only loads workflow entry files from:

  • .github/workflows/*.yml
  • .github/workflows/*.yaml

Subdirectories are not valid locations for workflow entry files.

Repository convention:

  1. Keep runnable workflow entry files at .github/workflows/ root.
  2. Keep cross-tooling/local CI scripts under dev/ or scripts/ci/ when used outside Actions.

Workflow behavior documentation in this directory:

  • .github/workflows/master-branch-flow.md