Skip to content

docs: simplify orphaned-stages rule description #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jakeva merged 1 commit into from
Mar 31, 2026
Merged

docs: simplify orphaned-stages rule description #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -234,9 +234,9 @@ Self-loops (`requisiteStageRefIds: ["1"]` on stage `"1"`) are also detected.

### `orphaned-stages` _(warning)_

Flags stages that are completely disconnected from the pipeline graph: they have no prerequisites of their own (`requisiteStageRefIds` is empty) **and** no other stage depends on them. These are isolated islands that Spinnaker will run unconditionally in parallel with the rest of the pipeline, which is usually unintentional.
Flags stages with no prerequisites and no dependents. These run unconditionally, independent of the rest of the pipeline.

This rule does **not** flag valid terminal stages (stages at the end of a dependency chain that nothing else depends on) — those have prerequisites and are a normal part of pipeline design.
Stages at the end of a dependency chain (prerequisites but no dependents) are not flagged.

Stages with an empty `refId` are skipped (caught by `required-stage-fields` instead).

Expand Down
Loading