oli/rdbms-playground
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

ci: gate feature branches via pull_request only (dedupe PR-push runs) #44

Merged
oli merged 1 commits from ci/dedupe-pr-runs into main 2026-06-24 10:33:17 +01:00
Conversation 0 Commits 1 Files Changed 1
+10 -5
1 changed files with 10 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/ci.yaml
+10 -5
View File
@@ -14,11 +14,16 @@
name: ci name: ci
on: on:
push: push:
# Branch pushes only — a tag push hits the same commit the branch push # Only `main` (the post-merge gate + canonical branch). Feature branches
# already gated, so `branches: ['**']` drops the redundant tag-triggered # are gated via `pull_request` instead. Running both on a push to a PR'd
# run (the release workflow owns tags). Pushing commits + a tag together # branch was pure duplication on Gitea: unlike GitHub it has no merge-
# still gates the commits via the branch push. # preview ref — its `pull_request` checks out `refs/pull/N/head`, the same
branches: ['**'] # commit a branch push would, so the two runs were byte-identical
# (docs.gitea.com/usage/actions/faq). Gating on `pull_request` is also
# forward-compatible: if Gitea ever adds the merge ref, these runs upgrade
# to testing the merged result for free. Tags stay unmatched (release.yaml
# owns them).
branches: [main]
# Skip the gate for changes that can't affect clippy/test — docs, markdown, # Skip the gate for changes that can't affect clippy/test — docs, markdown,
# and the website subproject (it has its own workflow, website.yaml, that # and the website subproject (it has its own workflow, website.yaml, that
# builds + publishes it). A push touching crate code *and* these still runs # builds + publishes it). A push touching crate code *and* these still runs