| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Removes 30 inherited workflows from anomalyco/opencode that don't apply to this fork (Discord webhooks, marketplace publishing, SaaS deploy infra, community moderation bots, OPENCODE_API_KEY-gated automations, Nix flake, Storybook). All would either fail loudly on missing secrets or remain inert because they target dev branch / upstream repo. Removes test.yml because it runs upstream's full unit + Playwright e2e against packages we do not ship (opencode, @opencode-ai/app). Retargets typecheck.yml from dev to main and switches off Blacksmith self-hosted runners. Calls 'bun typecheck' which is already filtered to our packages via the root package.json command.
|
The following comment was made by an LLM, it may be inaccurate: |
Sorry, something went wrong.
Adds step 3a immediately after the upstream merge in step 3. Without it, every sync from anomalyco/opencode reintroduces the 30 workflows we deleted in PR #14 (Discord, marketplace, SaaS deploy, moderation, etc.).
| Back | FazBrowse Home | New Git URL |
Summary
Cleans up the inherited GitHub Actions surface from anomalyco/opencode. Net result: only typecheck.yml (active CI on PRs) and release.yml (from PR #13, when merged) remain.
Removed (30 workflows)
Upstream secrets / SaaS infra:
Marketplace / publishing we don't own:
Community moderation (anomalyco-specific):
Nix flake (we don't ship):
Upstream test surface:
Modified (1 workflow)
Why delete vs disable-via-API
Disabling via gh workflow disable keeps inert YAMLs on disk and creates hidden state in GitHub's DB that's invisible to maintainers reading the repo. Deleting is honest: every remaining workflow is one we want.
Future syncs
When pulling from anomalyco/opencode, these deletions need to be re-applied (the upstream files will reappear in the merge). Consider a .gitattributes merge driver or a sync-time deletion script.