You asked for CI to re-run against the top of main whenever it updates. That already happens — on: push carries no branch filter, so every merge triggers a full run (job 353 after the last three merges: 141 unit + 10 integration, no skips).
I had also proposed a nightly run to catch external drift; you do not want one, so it is removed. What remains is just workflow_dispatch, a manual trigger for after a credential rotation or a budget top-up — which also retires the empty-commit trick I used earlier to make CI pick up newly added secrets.
Happy to close this entirely if you would rather leave the triggers alone.
You asked for CI to re-run against the top of main whenever it updates. **That already happens** — `on: push` carries no branch filter, so every merge triggers a full run (job 353 after the last three merges: 141 unit + 10 integration, no skips).
I had also proposed a nightly run to catch external drift; you do not want one, so it is removed. What remains is just `workflow_dispatch`, a manual trigger for after a credential rotation or a budget top-up — which also retires the empty-commit trick I used earlier to make CI pick up newly added secrets.
Happy to close this entirely if you would rather leave the triggers alone.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Pushes to main already trigger a full run, so code changes were
covered. What was not: the live tests depend on external state that
drifts with no commit at all — the LiteLLM budget filling up, a model
withdrawn from the proxy, a token revoked or expired. A nightly run
against the default branch surfaces that the morning it happens
instead of mid-task.
workflow_dispatch adds a manual trigger, which also removes the need
for the empty-commit trick used earlier to pick up new secrets.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
dev-agent
changed title from Run CI nightly and on manual dispatch to Add a manual CI trigger (workflow_dispatch)2026-09-07 20:40:13 +00:00
Operator does not want nightly or weekly runs. Pushes to main already
cover code changes, so the remaining addition is workflow_dispatch: a
manual re-run for after a credential rotation or a budget top-up,
which also retires the empty-commit trick used to pick up new secrets.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
You asked for CI to re-run against the top of main whenever it updates. That already happens —
on: pushcarries no branch filter, so every merge triggers a full run (job 353 after the last three merges: 141 unit + 10 integration, no skips).I had also proposed a nightly run to catch external drift; you do not want one, so it is removed. What remains is just
workflow_dispatch, a manual trigger for after a credential rotation or a budget top-up — which also retires the empty-commit trick I used earlier to make CI pick up newly added secrets.Happy to close this entirely if you would rather leave the triggers alone.
🤖 Generated with Claude Code
Run CI nightly and on manual dispatchto Add a manual CI trigger (workflow_dispatch)