Skip to content

ci: skip CI jobs for release-please bot PRs#77

Closed
aeneasr wants to merge 3 commits intomainfrom
worktree-ci-fix
Closed

ci: skip CI jobs for release-please bot PRs#77
aeneasr wants to merge 3 commits intomainfrom
worktree-ci-fix

Conversation

@aeneasr
Copy link
Copy Markdown
Member

@aeneasr aeneasr commented Apr 1, 2026

Summary

  • Adds if: github.actor != 'release-please[bot]' to all three CI jobs (test, lint, e2e)
  • Release-please PRs now show jobs as skipped instead of pending/failed, enabling auto-merge

Why

Release-please PRs don't need CI: the source branch (main) must already be green, and the release workflow validates on push to main. Without this filter, CI blocks auto-merge and requires a manual force-merge workaround.

Test plan

  • Confirm CI still runs on normal (non-release-please) PRs
  • Confirm next release-please PR shows CI jobs as skipped

🤖 Generated with Claude Code

aeneasr and others added 3 commits March 31, 2026 22:17
)

runSearch was calling setupIndexer with the raw indexRoot directory
instead of the SQLite db file path computed by config.DBPathForProject.
SQLite cannot open a directory and failed with:
  exec "PRAGMA journal_mode=WAL": unable to open database file

Also add os.MkdirAll for the db directory (matching the pattern in
runIndex) and a red/green regression test.

Closes #72

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Add `if: github.actor != 'release-please[bot]'` to all three jobs
(test, lint, e2e) so CI is skipped on automated release PRs. The
source branch must already be green before release-please opens a PR,
and the release workflow validates on push to main.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@aeneasr aeneasr closed this Apr 1, 2026
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