Repository navigation
Hub-spoke case study: wording matches the repo - #5
Merged
Merged
Conversation
…as run Claims now state what the code and workflows define, instead of present-tense results that imply a live deployment and passing CI runs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The case study read as if the pipeline had run and the network were live. The repo has one failed
proposerun and noapplyrun, so the claims now describe what the Terraform and workflows are built to do.propose.ymlinstead of "on every pull request"; "plan tests"updated→ 2026-11-07Build passes locally.