Skip to content
New issue

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

Rename this tool to mm-release? #140

Open
mcmire opened this issue Mar 12, 2024 · 0 comments
Open

Rename this tool to mm-release? #140

mcmire opened this issue Mar 12, 2024 · 0 comments

Comments

@mcmire
Copy link
Contributor

mcmire commented Mar 12, 2024

There are a couple of tickets which talk about adding new functionality that would not run automatically as part of the main workflow but only when requested:

To accomplish these, we may want to extend the CLI and introduce commands to this tool. We'd still have a default command for the existing workflow now so as not to break backward compatibility, but then we'd introduce commands for the two tickets above.

If we do this, then we may want to rename this tool to encapsulate the increase in scope. Perhaps we call it mm-release?

Zooming about a bit, we've been talking about creating a unified tool for all things MetaMask, so if we called it mm, then we could implement a Git-style interface such that mm <command> would map to mm-<command>. This would allow us to develop extensions to mm in independent repos and they would "just work". For instance, we could rename template-sync to mm-template-sync, and we could even create a new tool to make it easy to create a new repo based on the module template (mm-repo?). Naming this tool mm-release would fit into this plan.

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

No branches or pull requests

1 participant