ci: make PR validation unconditional - the paths filter silently skipped whole classes of pull requests #103
@@ -1,19 +1,18 @@
|
|||||||
name: PR Pipeline — Authorize → Validate → Review → Merge
|
name: PR Pipeline — Authorize → Validate → Review → Merge
|
||||||
|
# TRIGGER IS INTENTIONALLY UNFILTERED — DO NOT RE-ADD A `paths:` FILTER.
|
||||||
|
#
|
||||||
|
# This workflow previously carried `paths: ['**.prose.md', 'scripts/**.sh',
|
||||||
|
# '**.yaml', '**.yml']` on both `push` and `pull_request`. Any PR whose diff
|
||||||
|
# touched none of those patterns (for example a `deliverables/`-only PR, or a
|
||||||
|
# `scripts/*.py` / `bin/*` change) therefore produced NO Gitea Actions run at
|
||||||
|
# all: validation, lint, ai-review and the merge gate were silently skipped.
|
||||||
|
# Validation must run for every pull request and every push to master, so the
|
||||||
|
# trigger is deliberately unconditional.
|
||||||
on:
|
on:
|
||||||
push:
|
push:
|
||||||
branches: [master]
|
branches: [master]
|
||||||
paths:
|
|
||||||
- '**.prose.md'
|
|
||||||
- 'scripts/**.sh'
|
|
||||||
- '**.yaml'
|
|
||||||
- '**.yml'
|
|
||||||
pull_request:
|
pull_request:
|
||||||
types: [opened, synchronize, reopened]
|
types: [opened, synchronize, reopened]
|
||||||
paths:
|
|
||||||
- '**.prose.md'
|
|
||||||
- 'scripts/**.sh'
|
|
||||||
- '**.yaml'
|
|
||||||
- '**.yml'
|
|
||||||
|
|
||||||
jobs:
|
jobs:
|
||||||
auth:
|
auth:
|
||||||
|
|||||||
Reference in New Issue
Block a user