developer/scrabble-game
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

ci: skip the test-contour deploy on a no-code change #214

Merged
developer merged 1 commits from feature/ci-skip-deploy-on-docs into development 2026-07-07 21:27:47 +00:00
Conversation 1 Commits 1 Files Changed 1
+7 -3
developer commented 2026-07-07 21:22:50 +00:00
Owner
Copy Link
Copy Source

The deploy job was gated only on the event/ref, so a docs-only PR into development (where unit/integration/ui/conformance path-skip) still redeployed the test contour for nothing.

Gate deploy on the changes job too: it runs only when the Go or UI side actually changed. changes still defaults both to true when the diff is uncomputable, and a workflow/deploy edit forces both true, so ambiguous or infra changes still deploy as a safety net. A PR into master stays test-only; prod deploy is unaffected (separate manual workflow).

Note: this PR itself touches .gitea/workflows/, which forces the full suite + deploy — the docs-only skip will show on the next such PR.

The `deploy` job was gated only on the event/ref, so a docs-only PR into `development` (where `unit`/`integration`/`ui`/`conformance` path-skip) still redeployed the test contour for nothing. Gate `deploy` on the `changes` job too: it runs only when the Go or UI side actually changed. `changes` still defaults both to `true` when the diff is uncomputable, and a workflow/deploy edit forces both `true`, so ambiguous or infra changes still deploy as a safety net. A PR into `master` stays test-only; prod deploy is unaffected (separate manual workflow). Note: this PR itself touches `.gitea/workflows/`, which forces the full suite + deploy — the docs-only skip will show on the next such PR.
developer added 1 commit 2026-07-07 21:22:50 +00:00
ci: skip the test-contour deploy on a no-code change
CI / changes (pull_request) Successful in 1s
Details
CI / unit (pull_request) Successful in 11s
Details
CI / integration (pull_request) Successful in 15s
Details
CI / ui (pull_request) Successful in 1m6s
Details
CI / conformance (pull_request) Successful in 10s
Details
CI / gate (pull_request) Successful in 0s
Details
CI / deploy (pull_request) Successful in 1m44s
Details
4d1f389cf1 
The deploy job gated only on the event/ref, so a docs-only PR into
development (where unit/integration/ui/conformance path-skip) still
redeployed the test contour for nothing. Gate it on the `changes` job
too: deploy only when the Go or UI side changed. `changes` still
defaults both true when the diff is uncomputable, and a workflow/deploy
edit forces both true, so ambiguous or infra changes still deploy.
owner approved these changes 2026-07-07 21:23:50 +00:00
developer merged commit 3ad3b1dd7f into development 2026-07-07 21:27:47 +00:00
developer deleted branch feature/ci-skip-deploy-on-docs 2026-07-07 21:27:47 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
owner
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
owner (Ilia) developer
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: developer/scrabble-game#214
Delete Branch "feature/ci-skip-deploy-on-docs"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?