RabbitLabs/vylbot-app

Watch

Add cursor/* branches to test workflow (#559) #560

Open

Smithy-bot wants to merge 1 commit from cursor/559-test-workflow-cursor-branches into release/3.5.0

Smithy-bot commented

2026-08-29 17:19:21 +01:00

Member

Closes #559

Adds cursor/* to the push-trigger branch list in .forgejo/workflows/test.yml, so branches pushed by the bot get built and tested the same way feature/* and renovate/* already are.

 on:
   push:
     branches:
+      - cursor/*
       - feature/*
       - renovate/*

Branched from release/3.5.0 into cursor/559-test-workflow-cursor-branches, per the milestone convention for this repo.

Scope notes

.drone.yml has the same feature/* / renovate/* list, but it is the legacy Drone CI config rather than the active Forgejo Actions workflow, so it has been left alone.
stage.yml (main/develop/hotfix/release) and production.yml (tags) are deploy workflows and intentionally unchanged — bot branches should be tested, not deployed.
No other file in the repo references the trigger branch list.

This issue has no written acceptance criteria; I've taken the intent to be the test workflow's push-trigger list only. Happy to extend it if you wanted cursor/* covered elsewhere.

Closes #559 Adds `cursor/*` to the push-trigger branch list in `.forgejo/workflows/test.yml`, so branches pushed by the bot get built and tested the same way `feature/*` and `renovate/*` already are. ```diff on: push: branches: + - cursor/* - feature/* - renovate/* ``` Branched from `release/3.5.0` into `cursor/559-test-workflow-cursor-branches`, per the milestone convention for this repo. ### Scope notes - `.drone.yml` has the same `feature/*` / `renovate/*` list, but it is the legacy Drone CI config rather than the active Forgejo Actions workflow, so it has been left alone. - `stage.yml` (main/develop/hotfix/release) and `production.yml` (tags) are deploy workflows and intentionally unchanged — bot branches should be tested, not deployed. - No other file in the repo references the trigger branch list. This issue has no written acceptance criteria; I've taken the intent to be the test workflow's push-trigger list only. Happy to extend it if you wanted `cursor/*` covered elsewhere.

Smithy-bot added the

label

2026-08-29 17:19:21 +01:00

Smithy-bot added 1 commit

2026-08-29 17:19:21 +01:00

Add cursor/* branches to test workflow triggers (#559 )

Test / build (push) Successful in 1m4s

Details

5531730037

Smithy-bot commented

2026-08-29 17:19:35 +01:00

Author

Member

Self-check before handing this over for approval:

Diff is minimal — git diff release/3.5.0 against the branch is one added line in .forgejo/workflows/test.yml, nothing else (1 addition, 0 deletions, 1 file).
YAML still parses and the trigger resolves to push.branches = [cursor/*, feature/*, renovate/*]. The surrounding structure, indentation and quoting style are untouched, so there's no change to how Forgejo reads the rest of the file.
Ordering — put cursor/* first to keep the list alphabetical, matching the existing feature/*, renovate/* order.
Workflow steps pass on this branch locally (Node 22 rather than the 20.x the workflow pins, so treat this as indicative rather than identical to CI):
- yarn install --frozen-lockfile — clean
- yarn build (tsc) — clean
- yarn test (jest) — 1 suite, 5 tests, 1 snapshot, all passing
No side effects on deploys — stage.yml triggers on main/develop/hotfix/*/release/* and production.yml on tags, so a cursor/* push runs Test only and cannot reach an environment.
Not self-approving — over to you for review. Once this merges, the very next push to a cursor/* branch will exercise the trigger, which is the practical confirmation that it works.

Self-check before handing this over for approval: - **Diff is minimal** — `git diff release/3.5.0` against the branch is one added line in `.forgejo/workflows/test.yml`, nothing else (1 addition, 0 deletions, 1 file). - **YAML still parses** and the trigger resolves to `push.branches = [cursor/*, feature/*, renovate/*]`. The surrounding structure, indentation and quoting style are untouched, so there's no change to how Forgejo reads the rest of the file. - **Ordering** — put `cursor/*` first to keep the list alphabetical, matching the existing `feature/*`, `renovate/*` order. - **Workflow steps pass on this branch** locally (Node 22 rather than the 20.x the workflow pins, so treat this as indicative rather than identical to CI): - `yarn install --frozen-lockfile` — clean - `yarn build` (`tsc`) — clean - `yarn test` (`jest`) — 1 suite, 5 tests, 1 snapshot, all passing - **No side effects on deploys** — `stage.yml` triggers on `main`/`develop`/`hotfix/*`/`release/*` and `production.yml` on tags, so a `cursor/*` push runs Test only and cannot reach an environment. - **Not self-approving** — over to you for review. Once this merges, the very next push to a `cursor/*` branch will exercise the trigger, which is the practical confirmation that it works.

Smithy-bot changed title from ~~WIP: Add cursor/* branches to test workflow (#559)~~ to Add cursor/* branches to test workflow (#559)

2026-08-29 17:19:39 +01:00

Smithy-bot referenced this pull request

2026-08-29 17:19:54 +01:00

Add cursor/* branches to test workflow #559

Test / build (push) Successful in 1m4s

Required

Details

This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin cursor/559-test-workflow-cursor-branches:cursor/559-test-workflow-cursor-branches

git switch cursor/559-test-workflow-cursor-branches

Sign in to join this conversation.

No reviewers

No labels

good first issue

No milestone

No project

No assignees

1 participant

Notifications

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

RabbitLabs/vylbot-app!560

No description provided.