generated from MetaMask/metamask-module-template
-
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
ee238c2
commit 026679d
Showing
1 changed file
with
0 additions
and
92 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,95 +1,3 @@ | ||
| # MetaMask Design System | ||
|
|
||
| The MetaMask Design System contains shared UI components, design tokens, and tooling to ensure consistency and scalability across MetaMask web and mobile products. (WORK IN PROGRESS) | ||
|
|
||
| ## Instructions | ||
|
|
||
| Follow these instructions when using this template. | ||
|
|
||
| - Update the package name, referenced in the following places: | ||
| - [x] The `name` field of `package.json` | ||
| - [x] The README title | ||
| - [x] The README "Usage" section | ||
| - Update the package description | ||
| - [] The package description is referenced at the beginning of the README, and in the `description` field of `package.json`. | ||
| - [] Update the repository URL, referenced in the following places: | ||
| - `repository` field of `package.json` | ||
| - The links in the API section of the README | ||
| - [] If your project has side effects, update the `sideEffects` field of | ||
| `package.json` to `true`, or an array of file globs that match the files that | ||
| have side effects. | ||
| - [] Update the pull request template (`.github/pull_request_template.md`) to remove the `Examples` section that is specific to this template. | ||
| - [] Update the README "Usage" section, or remove it if it's not needed. | ||
| - [] Update the CODEOWNERS file to set the appropriate code owners for the repository (typically one or more engineering teams) | ||
| - [] Ensure each referenced team has write permission, and that the engineering team still has write permission. | ||
| - [] Delete these instructions. | ||
|
|
||
| ## Installation | ||
|
|
||
| This repository contains the following packages: | ||
|
|
||
| `yarn add @metamask/metamask-design-system/xyz` | ||
|
|
||
| or | ||
|
|
||
| `npm install @metamask/metamask-design-system/xyz` | ||
|
|
||
| ## API | ||
|
|
||
| See our documentation: | ||
|
|
||
| - [Latest published API documentation](https://metamask.github.io/metamask-design-system/latest/) | ||
| - [Latest development API documentation](https://metamask.github.io/metamask-design-system/staging/) | ||
|
|
||
| ## Contributing | ||
|
|
||
| ### Setup | ||
|
|
||
| - Install the current LTS version of [Node.js](https://nodejs.org) | ||
| - If you are using [nvm](https://github.com/creationix/nvm#installation) (recommended) running `nvm install` will install the latest version and running `nvm use` will automatically choose the right node version for you. | ||
| - Install [Yarn](https://yarnpkg.com) v4 via [Corepack](https://github.com/nodejs/corepack?tab=readme-ov-file#how-to-install) | ||
| - Run `yarn install` to install dependencies and run any required post-install scripts | ||
|
|
||
| ### Testing and Linting | ||
|
|
||
| Run `yarn test` to run the tests once. To run tests on file changes, run `yarn test:watch`. | ||
|
|
||
| Run `yarn lint` to run the linter, or run `yarn lint:fix` to run the linter and fix any automatically fixable issues. | ||
|
|
||
| ### Release & Publishing | ||
|
|
||
| The project follows the same release process as the other libraries in the MetaMask organization. The GitHub Actions [`action-create-release-pr`](https://github.com/MetaMask/action-create-release-pr) and [`action-publish-release`](https://github.com/MetaMask/action-publish-release) are used to automate the release process; see those repositories for more information about how they work. | ||
|
|
||
| 1. Choose a release version. | ||
|
|
||
| - The release version should be chosen according to SemVer. Analyze the changes to see whether they include any breaking changes, new features, or deprecations, then choose the appropriate SemVer version. See [the SemVer specification](https://semver.org/) for more information. | ||
|
|
||
| 2. If this release is backporting changes onto a previous release, then ensure there is a major version branch for that version (e.g. `1.x` for a `v1` backport release). | ||
|
|
||
| - The major version branch should be set to the most recent release with that major version. For example, when backporting a `v1.0.2` release, you'd want to ensure there was a `1.x` branch that was set to the `v1.0.1` tag. | ||
|
|
||
| 3. Trigger the [`workflow_dispatch`](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_dispatch) event [manually](https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow) for the `Create Release Pull Request` action to create the release PR. | ||
|
|
||
| - For a backport release, the base branch should be the major version branch that you ensured existed in step 2. For a normal release, the base branch should be the main branch for that repository (which should be the default value). | ||
| - This should trigger the [`action-create-release-pr`](https://github.com/MetaMask/action-create-release-pr) workflow to create the release PR. | ||
|
|
||
| 4. Update the changelog to move each change entry into the appropriate change category ([See here](https://keepachangelog.com/en/1.0.0/#types) for the full list of change categories, and the correct ordering), and edit them to be more easily understood by users of the package. | ||
|
|
||
| - Generally any changes that don't affect consumers of the package (e.g. lockfile changes or development environment changes) are omitted. Exceptions may be made for changes that might be of interest despite not having an effect upon the published package (e.g. major test improvements, security improvements, improved documentation, etc.). | ||
| - Try to explain each change in terms that users of the package would understand (e.g. avoid referencing internal variables/concepts). | ||
| - Consolidate related changes into one change entry if it makes it easier to explain. | ||
| - Run `yarn auto-changelog validate --rc` to check that the changelog is correctly formatted. | ||
|
|
||
| 5. Review and QA the release. | ||
|
|
||
| - If changes are made to the base branch, the release branch will need to be updated with these changes and review/QA will need to restart again. As such, it's probably best to avoid merging other PRs into the base branch while review is underway. | ||
|
|
||
| 6. Squash & Merge the release. | ||
|
|
||
| - This should trigger the [`action-publish-release`](https://github.com/MetaMask/action-publish-release) workflow to tag the final release commit and publish the release on GitHub. | ||
|
|
||
| 7. Publish the release on npm. | ||
|
|
||
| - Wait for the `publish-release` GitHub Action workflow to finish. This should trigger a second job (`publish-npm`), which will wait for a run approval by the [`npm publishers`](https://github.com/orgs/MetaMask/teams/npm-publishers) team. | ||
| - Approve the `publish-npm` job (or ask somebody on the npm publishers team to approve it for you). | ||
| - Once the `publish-npm` job has finished, check npm to verify that it has been published. |