Open rin-st opened 1 month ago
What do you think about naming convention for changesets? Because currently, it's a bit chaotic how we write it https://github.com/scaffold-eth/create-eth/releases
I think it would be good if we write it that way <scope>: <what was changed>
<scope>: <what was changed>
Possible scope's: cli, hardhat, foundry, next, external-extensions, curated-extensions, gh-actions, general? etc. Do we need to capitalize?
scope
For example cli: fix listr spamming curated-extensions: added eip-712
cli: fix listr spamming
curated-extensions: added eip-712
Or maybe just as conventional commits? What do you think?
Ohh yeah 100% agree! Love the scope idea too!
What do you think about naming convention for changesets? Because currently, it's a bit chaotic how we write it https://github.com/scaffold-eth/create-eth/releases
I think it would be good if we write it that way
<scope>: <what was changed>
Possible
scope
's: cli, hardhat, foundry, next, external-extensions, curated-extensions, gh-actions, general? etc. Do we need to capitalize?For example
cli: fix listr spamming
curated-extensions: added eip-712
Or maybe just as conventional commits? What do you think?