chore(ci): gate automatic workflow triggers to manual - #32
Open
mrhegemon wants to merge 1 commit into
Open
Conversation
Automatic triggers (push/pull_request/schedule) are replaced with workflow_dispatch so these workflows stop consuming billed GitHub-hosted minutes. The original trigger block is preserved as a comment above the replacement; `ci-local restore` puts it back exactly. workflow_dispatch inputs and workflow_call are carried across unchanged, so manual runs keep their form and reusable workflows keep working for callers. Checks move to local hardware via `ci-local run` and a pre-push hook. Gated 1 workflow(s). Capped artifact retention on 1.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
workflow_dispatch(manual runs only).retention-dayson 1 workflow(s). Actions storage is billed wherever the job ran, so gating alone does not reduce it.Why
Automatic triggers (push/pull_request/schedule) are replaced with
workflow_dispatch so these workflows stop consuming billed GitHub-hosted
minutes. The original trigger block is preserved as a comment above the
replacement;
ci-local restoreputs it back exactly.workflow_dispatch inputs and workflow_call are carried across unchanged, so
manual runs keep their form and reusable workflows keep working for callers.
Checks move to local hardware via
ci-local runand a pre-push hook.Gated workflows
docker-publish.ymlRetention capped
docker-publish.ymlReverting
The original triggers are preserved verbatim as a comment block above each replacement:
Deploy-on-merge and tag-triggered release workflows are deliberately left on their automatic triggers.