I recommend opening an issue before creating a PR.
- You must create a directory with the name of the command.
- Inside this directory, you must create a
doc.go
with a summary of the git command (based of the help of this command). - You must define all the options manually inside descriptions.json.
- Optionally, you could create a
<command>_custom.go
inside the command directory to add option(s) which cannot be generated. - You must run
make generate
to generate the<command>_gen.go
related to thedescriptions.json
. - Inside the command directory, you must add test
<command>_test.go
. - You must add examples inside example_test.go
Additionally, I use regular expressions to help with the descriptions.json
,
but the extracted information from the doc or the help is not useable directly,
manual editions are required.