os-sdlc: record the target in artifact.yml at intake and thread it through gates #303
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#303
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Promoted from #297 wrap-up. With --target given at setup, the stepper still asked ask_human 'which target', and every gate call needed --target/OS_SDLC_TARGET repeated. Recording the target in artifact.yml at intake removes the ask_human and the repetition, and should fix #301's stale 'project-config unresolved' prompt text.
Done: Artifact.create takes target:, attr_accessor :target, STRING_FIELDS includes target (artifact.rb). bin/os-sdlc:436 passes target: SELECTED_TARGET at intake. No 'which target' ask_human or '#301 project-config unresolved' strings remain in source. Closing.