chore(ci): keep upstream's GitHub workflows from running on our copy #2
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/no-upstream-ci"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
This is a copy of crabnebula-dev/qrtc, and Forgejo picked up upstream's
.github/workflowson it, so every push and PR started upstream's CI (clippy matrices, OpenSSL interop, SBOM check) on our shared runners. Forgejo reads.forgejo/workflowsfirst and only falls back to.github/workflowswhen that folder does not exist. This adds the folder with a README and no workflow files, so nothing runs. Our own workflows can go in the same folder later.Evidence
Runs started on the copy by pushing branches (Actions run list for
nanoya-biz/qrtc):.forgejo/workflows)fix/rusty-opus-1started run 9324, PR #1 started run 9330, and pushing an empty branch (09fb521) started run 9331.3a720e4started no run. The branch tip is3a720e4, and the run list still ends at 9331.Merge danger
Not verified / follow-ups: a merge from upstream that touches
.github/workflowsstill applies cleanly, since that folder is untouched.