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.
Finalize SPDD ADRs 26587–26827 and close remaining conformance/doc gaps #46628
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.
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
Uh oh!
There was an error while loading. Please reload this page.
Finalize SPDD ADRs 26587–26827 and close remaining conformance/doc gaps #46628
Changes from all commits
ceeabc7544b5a046f9cf3e9f9695ff35943d9aaf07File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/grill-with-docs] Section order in this file contradicts the lifecycle ordering just stated in the new guide above.
The "Choosing the Right Step Hook" guide (lines 11–17) lists hooks in execution order:
pre-steps→steps→pre-agent-steps→post-steps. But the sections below start with## Custom Steps (steps:)at line 21, followed by## Custom Pre-Checkout Steps (pre-steps:)here — the reverse of the lifecycle order. A reader scanning the headings will seesteps:documented beforepre-steps:, which directly contradicts the numbered guide.💡 Suggested fix
Move
## Custom Steps (steps:)after## Custom Pre-Checkout Steps (pre-steps:)so the section order matches the lifecycle order presented in the new guide. That way the page reads top-to-bottom in execution order: pre-steps → steps → pre-agent-steps → post-steps.@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/tdd] This assertion matches on literal YAML text fragments (
pre-agent-steps: []etc.) that may never actually appear in the generated output — making it a no-op rather than a real guard.If the compiler never emits such markers, the test always passes regardless of whether empty step blocks are suppressed. A stronger check would assert on the YAML structure directly or use an existing helper that parses the lock file.
💡 Suggested approach
Instead of checking for the absence of a string, assert that there are no empty
stepssequences in the parsed YAML, e.g. unmarshal the lock content and verify each top-level steps key is either absent or non-empty. Alternatively, document the exact serialised form the compiler could emit so the string guard has a known failure case.@copilot please address this.
Uh oh!
There was an error while loading. Please reload this page.