Skip to content

chore(ci): disable upstream workflows, keep only qBraid CI#10

Open
Kenny-Heitritter wants to merge 1 commit into
devfrom
chore/disable-upstream-workflows
Open

chore(ci): disable upstream workflows, keep only qBraid CI#10
Kenny-Heitritter wants to merge 1 commit into
devfrom
chore/disable-upstream-workflows

Conversation

@Kenny-Heitritter
Copy link
Copy Markdown
Member

Disables all upstream-inherited GitHub Actions on the fork by renaming them to .disabled (GitHub ignores non-.yml extensions). Prevents upstream publishing/deploying/releasing and repo-management bots from firing on qBraid/opencode.

Active workflows kept (3)

  • codeq-gcs-upload.yml — qBraid CodeQ binary build (5 platforms, qBraid branding) → gs://qbraid-codeq. Manual (workflow_dispatch) only.
  • test.yml — bun tests on PRs / dev push.
  • typecheck.yml — tsgo typecheck on PRs / dev push.

Disabled (renamed → .disabled)

Dangerous (publish/deploy under upstream identity):
publish.yml (npm/AUR/ghcr/Tauri desktop), deploy.yml (SST deploy), generate.yml (auto-commits to dev w/ upstream app secret), containers.yml (ghcr push), nix-hashes.yml, release-github-action.yml, publish-github-action.yml, publish-vscode.yml, sync-zed-extension.yml, beta.yml, stats.yml.

Upstream repo-management bots:
opencode.yml, review.yml, notify-discord.yml, pr-management.yml, pr-standards.yml, close-stale-prs.yml, stale-issues.yml, triage.yml, duplicate-issues.yml, daily-issues-recap.yml, daily-pr-recap.yml, docs-update.yml.

(nix-desktop.yml.disabled was already disabled upstream — left as-is.)

Why

Several of these triggered on push to dev (e.g. deploy.yml, generate.yml, publish.yml) and referenced upstream infra/registries/identity (opencode@sst.dev, registry.npmjs.org, AUR, Tauri signing, OPENCODE_APP_SECRET). They have no purpose on the qBraid fork and risk accidental publishing/deployment.

Reversible

Each is a rename only — re-enable by renaming .disabled.yml.

Notes

🤖 Generated with opencode

Disable (rename to .disabled) all non-qBraid workflows to prevent
upstream publishing/deploying/releasing and repo-management bots from
running on the fork.

Active workflows kept:
- codeq-gcs-upload.yml (qBraid binary build + GCS deploy, manual)
- test.yml, typecheck.yml (generic PR CI)

Disabled: publish, deploy, generate, containers, nix-hashes,
release/publish-github-action, publish-vscode, sync-zed-extension,
beta, stats, opencode, review, notify-discord, pr-management,
pr-standards, close-stale-prs, stale-issues, triage,
duplicate-issues, daily-issues-recap, daily-pr-recap, docs-update.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant