Repository navigation
Conversation
The build review now follows the journey a test walked (argos-ci/argos#2508): a section in "Review a build" for the journey order, the flow line and chip, the minimap and the ⇧←/⇧→ shortcuts, and the new `capture` field in the screenshot metadata reference, recorded by the SDKs (argos-ci/argos-javascript#360). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Collaborator
Author
|
Superseded by #256. This one was written against the |
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.
Documents the review-side scope of flows that ships with argos-ci/argos#2508 and argos-ci/argos-javascript#360 — nothing about the Flows tab, which stays in #248 for a later decision.
⇧←/⇧→; how the journey is derived (test title path, or story component) and what happens without the capture order (alphabetical within the journey). The shortcuts table gains the two keys.capturefield (index, 0-based capture order within the test) in the top-level table, its own section and the complete example.The screenshot is the one from #248 (the review with the flow line, minimap and chip), which is exactly this scope.
🤖 Generated with Claude Code