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
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,6 +129,16 @@ git fetch upstream
129
129
git rebase upstream/main
130
130
```
131
131
132
+
### 5. Add Changelog Entry
133
+
134
+
We use [towncrier](https://towncrier.readthedocs.io/) to manage our changelog. This prevents merge conflicts and ensures standardized release notes.
135
+
136
+
When you create a Pull Request, please add a changelog entry file in `docs/changes/devel/`. The file name should be the change type (e.g., `feature.rst`, `bugfix.rst`).
137
+
138
+
For detailed instructions and available types, see [docs/changes/README.md](https://github.com/mne-tools/mne-denoise/blob/main/docs/changes/README.md).
139
+
140
+
**Author Attribution**: We encourage contributors to include their name in the changelog entry if they wish to be highlighted. In Markdown, you can link to your GitHub profile (e.g., `... (by [@YourUser](...))`).
141
+
132
142
## Code Style
133
143
134
144
We use **Ruff** for linting and formatting, configured to follow PEP 8 with NumPy docstring conventions.
We use `towncrier` to manage our changelog. This ensures that changes are documented as they happen, preventing merge conflicts in the changelog file and ensuring high-quality release notes.
4
+
5
+
## Adding a Changelog Entry
6
+
7
+
When you make a change (feature, bugfix, documentation update), you should add a fragment file to the `docs/changes/devel/` directory.
8
+
9
+
The filename should be the type of change and the extension `.rst`. The PR number will be added automatically.
10
+
11
+
Format: `<TYPE>.rst`
12
+
13
+
### Available types:
14
+
15
+
*`feature`: New feature.
16
+
*`bugfix`: Bug fix.
17
+
*`doc`: Documentation improvement.
18
+
*`removal`: Deprecation or removal of a feature.
19
+
*`misc`: Internal changes, tooling, etc.
20
+
21
+
## Example
22
+
23
+
If you fixed a bug in a PR, create a file `docs/changes/devel/bugfix.rst`:
24
+
25
+
```rst
26
+
Fixed a bug where the ZapLine algorithm would crash on empty data.
0 commit comments