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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-75Lines changed: 3 additions & 75 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,81 +108,9 @@ You can use Gitpod (An Online Open Source VS Code like IDE which is free for Ope
108
108
109
109
[](https://gitpod.io/#https://github.com/TanStack/config)
110
110
111
-
## Commit message conventions
111
+
## Changesets
112
112
113
-
`TanStack/config` is using [Angular Commit Message Conventions](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines).
114
-
115
-
We have very precise rules over how our git commit messages can be formatted. This leads to **more readable messages** that are easy to follow when looking through the **project history**.
116
-
117
-
### Commit Message Format
118
-
119
-
Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
120
-
format that includes a **type**, a **scope** and a **subject**:
121
-
122
-
```
123
-
<type>(<scope>): <subject>
124
-
<BLANK LINE>
125
-
<body>
126
-
<BLANK LINE>
127
-
<footer>
128
-
```
129
-
130
-
The **header** is mandatory and the **scope** of the header is optional.
131
-
132
-
Any line of the commit message cannot be longer than 100 characters! This allows the message to be easier to read on GitHub as well as in various git tools.
133
-
134
-
### Type
135
-
136
-
Must be one of the following:
137
-
138
-
-**feat**: A new feature
139
-
-**fix**: A bug fix
140
-
-**docs**: Documentation only changes
141
-
-**style**: Changes that do not affect the meaning of the code (white-space, formatting, missing
142
-
semi-colons, etc)
143
-
-**refactor**: A code change that neither fixes a bug nor adds a feature
144
-
-**perf**: A code change that improves performance
145
-
-**test**: Adding missing or correcting existing tests
146
-
-**chore**: Changes to the build process or auxiliary tools and libraries such as documentation
147
-
generation
148
-
149
-
### Scope
150
-
151
-
The scope could be anything specifying place of the commit change. For example `useForm`, `useMutation` etc...
152
-
153
-
You can use `*` when the change affects more than a single scope.
154
-
155
-
### Subject
156
-
157
-
The subject contains succinct description of the change:
158
-
159
-
- use the imperative, present tense: "change" not "changed" nor "changes"
160
-
- don't capitalize first letter
161
-
- no dot (.) at the end
162
-
163
-
### Body
164
-
165
-
Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
166
-
167
-
### Footer
168
-
169
-
The footer should contain any information about **Breaking Changes** and is also the place to [reference GitHub issues that this commit closes](https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue).
170
-
171
-
**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
172
-
173
-
### Example
174
-
175
-
Here is an example of the release type that will be done based on a commit messages:
|`perf(pencil): remove graphiteWidth option`<br><br>`BREAKING CHANGE: The graphiteWidth option has been removed.`<br>`The default graphite width of 10mm is always used for performance reasons.`|~~Major~~ Breaking Release |
182
-
183
-
### Revert
184
-
185
-
If the commit reverts a previous commit, it should begin with `revert:`, followed by the header of the reverted commit. In the body it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
113
+
This repo uses [Changesets](https://github.com/changesets/changesets) to automate releases. If your PR should release a new package version (patch, minor, or major), please run run `pnpm changeset` and commit the file. If needed, changeset descriptions can be more descriptive, and will be included in the changelog. If your PR affects docs, examples, styles, etc., you probably don't need to generate a changeset.
186
114
187
115
## Pull requests
188
116
@@ -192,4 +120,4 @@ Use an appropriate commit type. Be especially careful with breaking changes.
192
120
193
121
## Releases
194
122
195
-
For each new commit added to `main` with `git push` or by merging a pull request or merging from another branch, a GitHub action is triggered and runs the `semantic-release` command to make a release if there are codebase changes since the last release that affect the package functionalities.
123
+
For each new commit added to `main`, a GitHub Workflow is triggered which runs the [Changesets Action](https://github.com/changesets/action). This generates a preview PR showing the impact of all changesets. When this PR is merged, the package will be published to NPM.
0 commit comments