Skip to content

Naming convention for changeset (discussion) #64

Open
@rin-st

Description

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?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions