You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* chore: setup changeset
* fix: temporary disable test run on CI
* chore: update workflow
* chore: update ci and docs
* chore: add build packages job
* Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,10 +102,35 @@ The root `package.json` file contains script delegates for common tasks:
102
102
-`yarn typecheck`: type-check files with TypeScript.
103
103
-`yarn lint`: lint files with [ESLint](https://eslint.org/).
104
104
-`yarn test`: run unit tests with [Jest](https://jestjs.io/).
105
+
-`yarn changeset`: create or update a Changeset for release notes and versioning.
105
106
-`yarn example start`: start the Metro server for the example app.
106
107
-`yarn example android`: run the example app on Android.
107
108
-`yarn example ios`: run the example app on iOS.
108
109
110
+
### Changesets workflow
111
+
112
+
Use [Changesets](https://github.com/changesets/changesets) to describe user-facing changes and prepare releases for the packages.
113
+
114
+
#### For contributors
115
+
116
+
- Add a Changeset for pull requests that change the public API, native behavior, runtime behavior, or developer-facing usage.
117
+
- You can usually skip a Changeset for changes that are purely internal, such as CI tweaks, refactors with no observable impact, or documentation-only updates.
118
+
- Run the following command from the repository root:
119
+
120
+
```sh
121
+
yarn changeset
122
+
```
123
+
124
+
- When prompted, select `@callstack/inspector` or `@callstack/inspector-cli`. Do not select the private example workspace.
125
+
- Choose the appropriate bump level (`patch`, `minor`, or `major`) and write a short summary of the user-facing change.
126
+
- Commit the generated file in `.changeset/` with the rest of your pull request.
127
+
128
+
#### For maintainers
129
+
130
+
- Pull requests merged to `main` with pending Changesets will cause the release workflow to open or update a Version Packages pull request.
131
+
- Review that release pull request carefully because it contains the generated version bump and changelog updates that will be published.
132
+
- After the Version Packages pull request is merged, the release workflow will build the package and publish it to npm automatically.
133
+
109
134
### Sending a pull request
110
135
111
136
> **Working on your first pull request?** You can learn how from this _free_ series: [How to Contribute to an Open Source Project on GitHub](https://app.egghead.io/playlists/how-to-contribute-to-an-open-source-project-on-github).
@@ -115,5 +140,6 @@ When you're sending a pull request:
115
140
- Prefer small pull requests focused on one change.
116
141
- Verify that linters and tests are passing.
117
142
- Review the documentation to make sure it looks good.
143
+
- Add a Changeset when the pull request introduces a user-facing change.
118
144
- Follow the pull request template when opening a pull request.
119
145
- For pull requests that change the API or implementation, discuss with maintainers first by opening an issue.
0 commit comments