chore(ci): delete scheduled paid reliability workflows - #140
Merged
Conversation
nightly-reliability.yml and tier3-public-gate.yml triggered on `schedule` and `workflow_dispatch` only, never on `pull_request`, so neither gated a merge. Both spent OPENAI_API_KEY on gpt models every single day. The benchmarks themselves are unchanged and still run on demand: `pnpm bench:local:nightly`, `pnpm bench:tier1:gate`, `pnpm bench:tier3:gate`, `pnpm reliability:scorecard`. The PR gates (ci.yml, tier1-gate.yml, tier2-staging-gate.yml) are untouched.
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.
nightly-reliability.yml(daily 09:00 UTC) andtier3-public-gate.yml(daily 11:00 UTC) both triggered onschedule+workflow_dispatchonly — never onpull_request— so neither gated a merge. Both spentOPENAI_API_KEYon gpt models on every scheduled run.Changed
.github/workflows/nightly-reliability.yml..github/workflows/tier3-public-gate.yml.docs/roadmap/browser-agent-ops.md: the P1 line "keep Tier 2 repeated gate and Tier 3 public gate healthy in CI" now points at the on-demandnpm run bench:tier3:gateinstead of a workflow that no longer exists.Untouched
The PR gates stay exactly as they were:
ci.yml,tier1-gate.yml,tier2-staging-gate.yml, pluschangesets.yml,publish-npm.yml,release.yml. No remaining workflow referenced either deleted file viauses:orworkflow_call.The benchmarks themselves are unchanged and still runnable locally:
pnpm bench:local:nightly,pnpm bench:tier1:gate,pnpm bench:tier3:gate,pnpm reliability:scorecard.RELIABILITY.mdanddocs/guides/benchmarks.mdalready document them as local commands, so they needed no edit.Secrets
No secret is orphaned.
OPENAI_API_KEYwas the only secret either deleted workflow used, andtier1-gate.ymlandtier2-staging-gate.ymlboth still need it.Now unscheduled (report only, nothing removed)
These npm scripts previously had a daily CI caller and now run on demand only:
bench:local:nightly,bench:tier1:gate,bench:tier3:gate,reliability:scorecard.bench:tier1:gateis also still invoked bytier1-gate.ymlon PRs.Verification
Ran
ci.yml's steps locally on this branch, capturing each exit code separately:pnpm lint(tsc --noEmit) — exit 0pnpm check:boundaries— exit 0, 271 filespnpm build— exit 0pnpm test— running against a freshly installed chromiumNo changeset: CI-only chore with no consumer-visible change, per
CLAUDE.md.