Repository navigation
Command composition / machine-readable output #10372
whatisaphone
started this conversation in
General
Replies: 1 comment
|
This (parsing human output) is currently the recommended and only way to "compose" commands together. Also see #10329 and the discussion linked there. Most of this would be made trivial by the eventual scripting language, but that isn't done yet. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Is there some generalized way to get machine-readable output from commands? Example:
That message shows up on stderr. I could capture stderr and parse it with a regex or something. But it seems saner to do something like this:
My use case is scripting/composition. For example, I'd like to be able to write a script that duplicates a commit, and also sets its description:
I don't see a good way to chain commands like this right now. Did I overlook something?
All reactions