polymech/zeroclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
c5fcda06ad
zeroclaw/.github/workflows
History
argenis de la rosa dd9e26eac6 ci: trigger website redeploy after release publish 
After publishing a beta or stable release, dispatch a
repository_dispatch event to zeroclaw-website so it rebuilds
with the latest version tag automatically.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-14 06:08:09 -04:00
..
checks-on-pr.yml ci: add x86_64-pc-windows-msvc to build matrix (#3449) 2026-03-13 21:45:08 -04:00
ci-run.yml ci: add x86_64-pc-windows-msvc to build matrix (#3449) 2026-03-13 21:45:08 -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 ci: add x86_64-pc-windows-msvc to build matrix (#3449) 2026-03-13 21:45:08 -04:00
README.md chore: update .gitignore, CODEOWNERS, and dependabot configuration 2026-03-07 21:05:23 -05:00
release-beta-on-push.yml ci: trigger website redeploy after release publish 2026-03-14 06:08:09 -04:00
release-stable-manual.yml ci: trigger website redeploy after release publish 2026-03-14 06:08:09 -04:00
tweet-release.yml ci: upgrade tweet-release with OpenClaw-style formatting, image support, and manual dispatch 2026-03-14 05:01:56 -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