Files
grm/docs/specs/GRM-172.md
T
emil 1b315e0aba
Post-merge / detect-and-configure (push) Successful in 1m1s
Post-merge / release-and-maintain (push) Successful in 54s
GRM-172: ci: docs fast-path, notify-failure scoping, post-merge queue
Co-authored-by: emil User <emil.simeonov@tutanota.com>
2026-09-21 20:21:20 +00:00

44 lines
1.4 KiB
Markdown

# GRM-172: CI hygiene — docs fast-path, failure-notify scoping, post-merge cancel
## Problem
GRM CI has the same inefficiencies fixed in infra (OBL-INFRA-613/615/616):
docs-only PRs run the full quality suite, CI failures auto-create issues
(noise — issues are for deploy failures only), and post-merge
`cancel-in-progress: true` can kill a release mid-publish.
## Approach
REQ-1: Docs-only PRs skip heavy validate steps (lint-all, unit tests,
translation check, test-speed, security scan, workflow dry-run). Docs
gate, spec validation, PR size, and auto-merge preconditions still run.
Restricted to pull_request events.
REQ-2: Remove the failure-issue step from `ci.yml` validate job.
Post-merge keeps failure notification (release/publish failures are
deploy-pipeline events).
REQ-3: post-merge `cancel-in-progress: false` — queue instead of killing
an in-flight release/publish.
## Test Plan
- `make workflow-lint` passes.
- Docs-only PR: quality steps skipped, gates still run.
- Non-docs PR: unchanged behavior.
## Deploy Plan
Workflow-only change; takes effect on merge. No release needed.
## Rollback Plan
Revert the commit.
## Acceptance Criteria
- [x] REQ-1 implemented — early docs-only step + step-level `if` gates
- [x] REQ-2 implemented — notify step removed from ci.yml only
- [x] REQ-3 implemented — post-merge concurrency flipped
- [x] `make workflow-lint` passes