tiennm99/ccs
1
0 Fork 0
mirror of https://github.com/tiennm99/ccs.git synced 2026-10-14 04:15:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: restrict bar release workflow to main (#1612)

Browse Source
This commit is contained in:
Kai (Tam Nhu) Tran authored and GitHub committed 2026-06-30 12:21:33 -04:00
1 parent 2282e15a99
commit 23b2c3d6af
2 files changed
+7 -3
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/ccs-bar.md
+2 -2
View File
@@ -126,10 +126,10 @@ The app ships as a single floating GitHub release asset, `CCS-Bar.app.zip` under
The `Bar Release` workflow (`.github/workflows/bar-release.yml`) builds and publishes the asset automatically. It is scoped tightly so it never affects other PRs or CI:
- It runs only on a push to `main` that touches `macos-bar/**`, or a manual run from the Actions tab (`workflow_dispatch`).
- It runs only on a push to `main` that touches `macos-bar/**`, or a manual run from the Actions tab (`workflow_dispatch`) when the selected ref is `main`.
- It runs only on the dedicated self-hosted macOS runner (label `ccs-bar`); the Linux CI runners never pick it up and it never competes for them.
So bar changes reach users when they land on `main` (the stable cadence). To cut a release without a code change, or to re-publish, trigger the workflow manually.
So bar changes reach users when they land on `main` (the stable cadence). To cut a release without a code change, or to re-publish, trigger the workflow manually with `main` selected as the workflow ref.
### Manual fallback