Repository navigation
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.
docs(exodia): correct /exodia:fix P0 invocation + agent counts + ARCHITECTURE after the v3 collapse (v3.0.1) #310
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
docs(exodia): correct /exodia:fix P0 invocation + agent counts + ARCHITECTURE after the v3 collapse (v3.0.1) #310
Changes from all commits
c0672cfFile 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.
The new handoff requires
/exodia:fix "<finding-id>" P0, but the final P0 report template immediately above still only prints#, category, issue, and location, so a user following the generated mega-swarm report has no visiblefinding.idto copy. Sincefixfilters by an exactfinding.idmatch, this makes the documented auto-inherit path fail unless the user manually opens.eight-gates/artifacts/findings.json; add an ID column or otherwise print the persisted IDs in the report before using them as the next command argument.Useful? React with 👍 / 👎.
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.
This P0 follow-up command omits the third
maximumargument, so it runs/exodia:fixwith severity P0 but defaultstandardparallelism. The same commit updates the fix docs to say a P0 emergency should passP0 maximum, and this section is specifically the “P0 Issues (Fix Immediately)” handoff from mega-swarm, so users following it do not get the intended maximum P0 pass; make the example/exodia:fix "<finding-id>" P0 maximum.Useful? React with 👍 / 👎.
Uh oh!
There was an error while loading. Please reload this page.