Skip to content

docs(review): review a journey in order - #252

Closed
jsfez wants to merge 1 commit into
mainfrom
flows-review-context
Closed

jsfez wants to merge 1 commit into
mainfrom
flows-review-context

Conversation

@jsfez

@jsfez jsfez commented Aug 18, 2026

Copy link
Copy Markdown
Collaborator

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.

  • Review a build — a new "Review a journey in order" section: journey order inside each status section, the flow line and Metadata chip, the flow minimap, ⇧←/⇧→; 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.
  • Screenshot metadata — the capture field (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

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>
@jsfez

jsfez commented Sep 12, 2026

Copy link
Copy Markdown
Collaborator Author

Superseded by #256. This one was written against the flows-review-context branch and documents three things that were deliberately left out of argos-ci/argos#2573: journey ordering of the diff list, the flow line above the screenshot name, and the Metadata flow chip. Its screenshot shows that same UI.

@jsfez jsfez closed this Sep 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant