Skip to content

Conversation

shristibaral
Copy link
Contributor

Reference issue (if any)

Fixes #13372

What does this implement/fix?

I changed the word Enhancement to newfeature in line 617 of file contribution.rst as Enhancement is not a recognized change type.

Additional information

@shristibaral shristibaral changed the title Changes in documentation #13372 Changes in documentation Aug 12, 2025
@shristibaral shristibaral changed the title Changes in documentation "Enhancement" changed to "newfeature" in contribution guide documentation Aug 12, 2025
shristibaral added a commit to shristibaral/mne-python that referenced this pull request Aug 12, 2025
@shristibaral shristibaral changed the title "Enhancement" changed to "newfeature" in contribution guide documentation ENH: "Enhancement" changed to "newfeature" in contribution guide documentation Aug 12, 2025
@shristibaral shristibaral changed the title ENH: "Enhancement" changed to "newfeature" in contribution guide documentation "Enhancement" changed to "newfeature" in contribution guide documentation Aug 12, 2025
@shristibaral shristibaral marked this pull request as ready for review August 12, 2025 13:56
@drammock
Copy link
Member

could you also fix the "devel" -> "dev" problem you mentioned in #13372 @shristibaral?

@cbrnr can you handle review of this one when it's ready?

@cbrnr
Copy link
Contributor

cbrnr commented Aug 12, 2025

Sure. Is the change from enhancement to newfeature OK (i.e., can Towncrier handle it)?

@shristibaral
Copy link
Contributor Author

shristibaral commented Aug 12, 2025

could you also fix the "devel" -> "dev" problem you mentioned in #13372 @shristibaral?

I think someone has already fixed it. It isn't there in the code anymore. Just in the live documentation.

@drammock
Copy link
Member

Sure. Is the change from enhancement to newfeature OK (i.e., can Towncrier handle it)?

@cbrnr a quick scan of the filenames in doc/changes/dev shows lots of NNNNN.newfeature.rst files. So, yes.

could you also fix the "devel" -> "dev" problem you mentioned in #13372 @shristibaral?

I think someone has already fixed it. It isn't there in the code anymore. Just in the live documentation.

In that case we should backport this PR (once merged) and also the change that updated that line of the contrib guide (probably not the whole PR, just that one line). @cbrnr are you up for that?

@cbrnr cbrnr enabled auto-merge (squash) August 13, 2025 08:16
@cbrnr
Copy link
Contributor

cbrnr commented Aug 13, 2025

Thanks @shristibaral!

@drammock
Copy link
Member

@cbrnr merging is blocked until you re-review and "approve" (to cancel out the "request changes" review)

@cbrnr
Copy link
Contributor

cbrnr commented Aug 13, 2025

@drammock there's a failing test though, I'll restart.

@drammock
Copy link
Member

test has failed 3 times at the same spot. Appears to be on a mkdir -p command, which is odd. May have something to do with recent migration of macos-latest to macos-15. Will investigate when I have time, if someone else doesn't beat me to it.

@cbrnr cbrnr merged commit be5fcef into mne-tools:main Aug 14, 2025
32 checks passed
zEdS15B3GCwq pushed a commit to zEdS15B3GCwq/mne-python that referenced this pull request Aug 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inconsistencies in the documentation of Contribution guide
5 participants