Uh oh!
There was an error while loading. Please reload this page.
docs(skills): canonical responder-extraction command on the incident card - #167
Merged
Conversation
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
What
The incident reference card (
skills/flashduty/reference/incident.md) did not document where an incident's responders (assignees) live in the output or how to extract them with resolved person names, so automation had to probe multiple command variants to findresponders/person_name.Changes
detail <id> --json | jq '.responders[]'.person_id,person_name,email,assigned_at,acknowledged_at,as), thegettop-level-array difference, and the two projection traps (listdefault compact projection omitsresponders;detail --fieldsonly prints named fields).Verification (code-traced, no live creds)
internal/cli/incident.go:getprintsresult.Items(top-level array) in structured mode;detailprints a singleIncidentInfo; plain-text paths print aResponders: name1, name2line.go-flashdutyv0.14.2models_gen.go:IncidentInfo.Responders []Responder;Respondercarriesperson_id/person_name/email/assigned_at/acknowledged_at/as, withperson_nameandemailfilled by the server.make check-cards→skilldoc: cards OK;go test ./internal/skilldoc/→ ok.