bookmark set/create: take change hashes as bookmark show --json prints them issue #103 closed: completed andymccall opened this · 2 comments
issue #103 closed ← closed by proposal #106 A full change hash resolves without its # (#103) landed
andymccall set labels bug, gap ·
andymccall referenced by change c86270b7c670 on bare-hashes ·
closed by change aa4939e07a09 ·
andymccall reopened ·
Reopened after proposal #106 landed: the bare-hash half is done; the second half (say in bookmark create --only's help that it leaves out changes C does not depend on, and suggest bookmark set NAME <main's heads> C) remains.
andymccall referenced by change b9bf7eec1f2d on only-help-103 ·
Both halves are in: bare 64-hex hashes are accepted (proposal #106), and bookmark create --only / bookmark set --only say in their help that other changes to the same files are left out, so a file can come out partly edited, and suggest bookmark set NAME <its heads> CHANGE instead. Closing.
andymccall closed ·
Found 2026-10-11 while splitting a fix onto its own bookmark:
oxy bookmark show main --jsonprints heads as bare hex hashes, butoxy bookmark set NAME HASH..answers 'no change matches "a36bab6b…"' until each is written#a36bab6b…. Ask: accept a full 64-hex change hash with or without#(it cannot be a change ID, which is shorter), so JSON output feeds back into commands. Related:bookmark create --only Cgives C and its dependencies only, which may leave out other changes to files C's state includes (here .flow/pipeline.kdl came out half-edited and CI could not parse it); the help could say so and suggestbookmark set NAME <main's heads> C.