The Deployment Automation (@smartcontractkit/deployment-automation) team is responsible for the development and maintenance of this repo, and are the primary code owners and reviewers.
- Open a branch from
main
and give it a descriptive name. - Make changes on your branch.
- When you are ready to submit your changes, create a changeset with
pnpm changeset
and commit the changeset file. - Push your branch and open a PR against
main
. - Ensure your PR passes all CI checks.
- Request a review from the Deployment Automation team (@smartcontractkit/deployment-automation).
Changesets are a way to manage changes to the codebase that are not yet released. Here are a few things to keep in mind when you create a changeset:
- Following semantic versioning, select between: major, minor and patch
- MAJOR version when you make incompatible API changes
- MINOR version when you add functionality in a backwards compatible manner
- PATCH version when you make backwards compatible bug fixes.
- When describing the change, try to answer the following:
- WHAT the change is
- WHY the change was made