Updated Changesets (markdown)

Tyler Butler 2023-10-05 09:58:36 -07:00
Родитель 69e96ad52c
Коммит 0e6008ad20
1 изменённых файлов: 2 добавлений и 2 удалений

@ -59,11 +59,11 @@ You can add a changeset to your PRs manually or by using the `pnpm flub changese
### Adding a changeset using `pnpm flub changeset add`
To add a changeset, run `pnpm flub changeset add` from the root of the repo. You will be prompted to select the affected packages. By default the CLI will show what packages have changed relative to `main` to make it easier to select affected packages, but you can compare with any branch by passing the `--branch <BRANCH>` flag (e.g. `--branch next`. The output is completely editable after the CLI is used so don't worry about "getting it right." You can always fix it up!
To add a changeset, run `pnpm flub changeset add` from the root of the release group. You will be prompted to select the affected packages. By default the CLI will show what packages have changed relative to `main` to make it easier to select affected packages, but you can compare with any branch by passing the `--branch <BRANCH>` flag (e.g. `--branch next`. The output is completely editable after the CLI is used so don't worry about "getting it right." You can always fix it up!
### Manually adding a changeset
To manually add a changeset, add a randomly named markdown file to the `.changeset` folder in the root of the repo. Make sure to include the metadata about what packages are affected!
To manually add a changeset, add a randomly named markdown file to the `.changeset` folder in the root of the release group. Make sure to include the metadata about what packages are affected!
### Adding an empty changeset