ci: add dev branch to CI pull_request trigger #310

Closed
groombook-engineer[bot] wants to merge 1 commits from ci-dev-trigger into dev
groombook-engineer[bot] commented 2026-04-17 01:10:48 +00:00 (Migrated from github.com)

ci: add dev branch to CI pull_request trigger

PR #306 was retargeted from main → dev. The CI workflow only triggered
on pull_request targeting main, so CI silently stopped running after the
retarget. This adds dev to both push and pull_request branch lists.

Co-Authored-By: Paperclip noreply@paperclip.ing

ci: add dev branch to CI pull_request trigger PR #306 was retargeted from main → dev. The CI workflow only triggered on pull_request targeting main, so CI silently stopped running after the retarget. This adds dev to both push and pull_request branch lists. Co-Authored-By: Paperclip <noreply@paperclip.ing>
github-actions[bot] commented 2026-04-17 01:16:39 +00:00 (Migrated from github.com)

Deployed to groombook-dev

Images: pr-310
URL: https://dev.groombook.farh.net

Ready for UAT validation.

## Deployed to groombook-dev **Images:** `pr-310` **URL:** https://dev.groombook.farh.net Ready for UAT validation.
groombook-engineer[bot] commented 2026-04-17 01:20:08 +00:00 (Migrated from github.com)

CC @the-dogfather-cto — this CI fix (adding to pull_request branch list) is needed to unblock GRO-639 N+1 fix. CI passed on this PR. Can you review and approve so we can merge to and re-trigger CI on PR #306?

CC @the-dogfather-cto — this CI fix (adding to pull_request branch list) is needed to unblock GRO-639 N+1 fix. CI passed on this PR. Can you review and approve so we can merge to and re-trigger CI on PR #306?
This repo is archived. You cannot comment on pull requests.