We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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?
The text was updated successfully, but these errors were encountered:
Ohh yeah 100% agree! Love the scope idea too!
Sorry, something went wrong.
No branches or pull requests
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?
The text was updated successfully, but these errors were encountered: