chore(ci): keep upstream's GitHub workflows from running on our copy #2

Merged
shjackal merged 1 commit from chore/no-upstream-ci into main 2026-11-01 20:13:31 +01:00
Owner

Summary

This is a copy of crabnebula-dev/qrtc, and Forgejo picked up upstream's .github/workflows on it, so every push and PR started upstream's CI (clippy matrices, OpenSSL interop, SBOM check) on our shared runners. Forgejo reads .forgejo/workflows first and only falls back to .github/workflows when 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):

Before (no .forgejo/workflows) After (this branch)
Push of fix/rusty-opus-1 started run 9324, PR #1 started run 9330, and pushing an empty branch (09fb521) started run 9331. Push of 3a720e4 started no run. The branch tip is 3a720e4, and the run list still ends at 9331.

Merge danger

  • Door: two-way. Deleting the folder brings upstream's CI back.
  • Blast radius: none for builds or for RKD. The only effect is that no CI runs on this copy until we add our own workflows.

Not verified / follow-ups: a merge from upstream that touches .github/workflows still applies cleanly, since that folder is untouched.

## Summary This is a copy of crabnebula-dev/qrtc, and Forgejo picked up upstream's `.github/workflows` on it, so every push and PR started upstream's CI (clippy matrices, OpenSSL interop, SBOM check) on our shared runners. Forgejo reads `.forgejo/workflows` first and only falls back to `.github/workflows` when 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`): | Before (no `.forgejo/workflows`) | After (this branch) | | --- | --- | | Push of `fix/rusty-opus-1` started run 9324, PR #1 started run 9330, and pushing an empty branch (`09fb521`) started run 9331. | Push of `3a720e4` started no run. The branch tip is `3a720e4`, and the run list still ends at 9331. | ## Merge danger - **Door:** two-way. Deleting the folder brings upstream's CI back. - **Blast radius:** none for builds or for RKD. The only effect is that no CI runs on this copy until we add our own workflows. Not verified / follow-ups: a merge from upstream that touches `.github/workflows` still applies cleanly, since that folder is untouched.
Forgejo reads .forgejo/workflows first and only falls back to
.github/workflows when that folder does not exist. Add the folder with a
README and no workflow files, so upstream's CI (clippy matrices, OpenSSL
interop, SBOM check) stops using our shared runners. Our own workflows
can go in the same folder later.
Commenting is not possible because the repository is archived.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
nanoya-biz/qrtc!2
No description provided.