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
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,14 @@ We're always looking for more opinions on discussions in the issue tracker. It's
26
26
- For ambitious tasks, you should try to get your work in front of the community for feedback as soon as possible. Open a pull request as soon as you have done the minimum needed to demonstrate your idea. At this early stage, don't worry about making things perfect, or 100% complete. Add a `[WIP]` prefix to the title, and describe what you still need to do. This lets reviewers know not to nit-pick small details or point out improvements you already know you need to make.
27
27
- Don't include unrelated changes
28
28
- New features should be accompanied with tests and documentation
29
-
- Use a clear and descriptive title for the pull request and commits
29
+
- Commit messages
30
+
- Use a clear and descriptive title for the pull request and commits
31
+
- We use [semantic-release](https://www.npmjs.com/package/semantic-release) to automatically generate release
32
+
notes, versions and publish releases. This requires commit messages must be formatted properly using
0 commit comments