Add JSON output mode#65
Open
sato820 wants to merge 1 commit into
Open
Conversation
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 free
to 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.
Fixes #2.
Adds a machine-readable
--jsonoutput mode for git-context while preserving the existing Markdown output.What changed:
--jsonto both the standalonegit-contextscript and the installed package entry point.--outputworking in JSON mode and writes files as UTF-8.--jsonusage in the README.Verified locally:
python git-context --dir . --jsonparses as valid JSON.git_context.main()parses as valid JSON.python git-context --dir . --depth 1still produces Markdown output.python git-context --dir . --json -o <file>writes valid JSON.Bounty payout: BTC on-chain
bc1q4zlvgnskuxmrnywk2y8klcdjf4zmkjau0e5srm. I can also provide a fresh Lightning invoice on acceptance if that is easier for the $2 payout.