Skip to content

ci: only run CI on release-please PRs and release tags#260

Merged
CalebisGross merged 1 commit intomainfrom
ci/release-only
Mar 20, 2026
Merged

ci: only run CI on release-please PRs and release tags#260
CalebisGross merged 1 commit intomainfrom
ci/release-only

Conversation

@CalebisGross
Copy link
Copy Markdown
Collaborator

Summary

  • CI now skips regular feature and dependabot PRs entirely — saves Action minutes
  • Runs as a pre-release gate on release-please PRs (release-please--* branches)
  • Runs as a final check on v* tag pushes (alongside the release build)
  • workflow_dispatch preserved as an escape hatch for manual runs
  • Day-to-day quality relies on local pre-commit hooks (go fmt, go vet, golangci-lint)

How it works

A lightweight should-run job checks the trigger context:

  • Tag push or workflow_dispatch: always runs
  • PR from release-please--* branch: runs
  • Any other PR: all jobs skip (show as "skipped" in GitHub, not "failed")

Test plan

  • Open a regular feature PR — verify CI jobs show as skipped
  • Merge enough conventional commits for release-please to open a PR — verify CI runs on it
  • Manual trigger via Actions tab — verify CI runs

🤖 Generated with Claude Code

Regular feature and dependabot PRs now skip CI entirely, relying on
local pre-commit hooks (go fmt, go vet, golangci-lint) for quality.
CI runs as a pre-release gate on release-please PRs and as a final
check on v* tag pushes. workflow_dispatch preserved as an escape hatch.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@CalebisGross CalebisGross merged commit 5522ff0 into main Mar 20, 2026
6 checks passed
@CalebisGross CalebisGross deleted the ci/release-only branch March 20, 2026 15:17
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