@dennisseah you mean when a <command>.json file is updated we should regenerate the documentation has a pre-commit step?

@dennisseah you mean when a <command>.json file is updated we should regenerate the documentation has a pre-commit step?

yes, how to do this in pre-commit hook?

we use husky for pre-commit hooks. You can add to the husky.hooks.pre-commit script it package.json

we use husky for pre-commit hooks. You can add to the husky.hooks.pre-commit script it package.json

I do not know how to do this. Will reach out to you. thanks

Content edits will be handled in a separate issue, otherwise LGTM.

@jmspring these are generated content from command json files, people forgot to generate them in previous PRs. And this will never happen again because @evanlouie showed me how to add git pre-commit hook. thanks