Monorepo Changesets

This is an example of a possible structure and tooling for a Mailchimp Open Commerce Monorepo.

Development workflow

1. Create a feature branch.
2. Add a changeset (if the changes should result in a new version):

   npx run changeset
   

3. Update the new file created in the previous step on .changeset/[file-name].md you need to put more detail.
4. Commit and push changes to the branch.
5. Create a pull request.
6. Merge the pull request into the main (default) branch.
7. Repeat the above previous steps when making new changes.

Release workflow

1. When ready for a release, go to the Action tab on github repo and run the Release workflow .
2. If the pull request contained a changeset, the changesets action will create a Version Packages pull request
3. Continue merging changes into the main (default) branch
4. Merge the "Version Packages" pull request to trigger a release

Compare with nx + semantic-release

Advantage:

• The changeset descriptions are editable after creation, and a user can go in and change this as they desire.
• Unopinionated about your git workflows, with squashing and modifying commits being completely safe, without fear of breaking a release.

Disadvantage:

• Manual adding changeset.
• The contributors need to learn a new workflow.