I use a script that post processes what knope computes out as changesets due to how it treats packages that are not in a scope, or ehere it may not strictly follow conventional commit rules. ATM I have to do a lot of regex on the output.
It would be much better for the dry run to be able to output a JSON structure to parse on. My script generates changesets itself based on what knope finds.
I use a script that post processes what knope computes out as changesets due to how it treats packages that are not in a scope, or ehere it may not strictly follow conventional commit rules. ATM I have to do a lot of regex on the output.
It would be much better for the dry run to be able to output a JSON structure to parse on. My script generates changesets itself based on what knope finds.