config_write_command.rb origin remote via Backlog::Issues::ShellRunner (#635c) #704
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
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
rule-proposal
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#704
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?
Problem
config_write_command.rbuses a bare backtick to look up the origin remote instead of the plugin's own shell abstraction. This bypassesBacklog::Issues::ShellRunner#capture, which already wrapsOpen3.capture3and returns[out, success?].Observed
Verified on main today (2026-09-24).
plugins/os-backlog/lib/backlog/config_write_command.rb:39-41uses a bare backtick,`git remote get-url origin 2>/dev/null`.strip, instead of the plugin's ownBacklog::Issues::ShellRunner#capture(*cmd), which wrapsOpen3.capture3and returns[out, success?](stderr discarded, preserving the2>/dev/nullsemantics).tests/cli_config_write_command_test.rbruns in a non-git tmpdir, so the remote resolves tonileither way — this test does not distinguish the two implementations.Reproduce
Approach
config_write_command.rb'sorigin_remotecallsBacklog::Issues::ShellRunner.new.capture('git', 'remote', 'get-url', 'origin')and treats the result asnilunless the call succeeded and the output is non-empty.Required work:
config_write_command.rbwithBacklog::Issues::ShellRunner#capture— check:grep -n '`git' plugins/os-backlog/libreturns nothing.cli_config_write_command_test.rbstill passes (remotenilin its non-git tmpdir either way).Rejected: an ENV variable override for the binary or remote lookup (out of scope; not the fragility this ticket addresses). Merging plugin load paths (a deliberate process boundary, not an accident to fix by removing it).
Non-goals: changing what happens when the origin lookup legitimately fails for a reason other than bypassing the shell abstraction. No ADR change.
VERDICT: CREATE
Acceptance criteria
config_write_command.rbneeds the origin remote, when it looks it up, then it callsBacklog::Issues::ShellRunner#capture, not a bare backtick, and returnsnilunder the same conditions as before (call fails or output empty).Owner sketch
Non-goals
Origin
ShellRunnerabstraction ← DESIGN, plugins are separate load paths by design (not a bug to fix by merging them).Work started in session 082c3e8b on branch ticket-704 via /os-sdlc:implement.
Resolution
Done: ConfigWriteCommand#origin_remote calls Backlog::Issues::ShellRunner#capture for the origin remote and returns nil unless the call succeeds with non-empty output. No bare backtick remains in plugins/os-backlog/lib.
Evidence: Pipeline implementation 34, 11 dispatches, implementation_complete. New test plugins/os-backlog/tests/cli_config_write_origin_remote_test.rb; os-backlog suite green at suite-check. Commit
82f374d2on branch ticket-704.Follow-ups: none