ci(workflows): Docs-Aenderungen von CI ausschliessen #272
No reviewers
Labels
No labels
component/backend
component/docs
component/e2e
component/frontend
component/infra
component/keycloak
prio/high
prio/low
prio/medium
type/bug
type/chore
type/feature
type/refactor
type/test
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
WompSchmiede/FamilienFeierPlaner!272
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/ci-skip-worktree"
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?
Allgemein
Altes Verhalten
Jeder PR triggert ci-backend, ci-frontend und e2e,
auch wenn nur docs/, README.md oder AGENTS.md geaendert wurden.
Neues Verhalten
paths-ignoreauf pull_request-Trigger in ci-backend.yml, ci-frontend.yml, e2e.ymlci-docs-only.yml-Workflow meldet dieselben 5 Job-Namen mit Success (Dummy-Steps)Begruendung
Ressourcenverschwendung vermeiden. Docs-Aenderungen brauchen keine Builds, Lint, Tests oder E2E-Runs.
Test-Hinweise
Nach Merge: Einen Docs-Only-PR erstellen und pruefen, ob nur
CI Docs Only / lint-backend,CI Docs Only / test-backend,CI Docs Only / lint-frontend,CI Docs Only / test-frontend,CI Docs Only / e2eundCI Meta / conventional-commitlaufen.Checkliste