Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

A single changelog file instead of two #5728

Closed
Pierre-Sassoulas opened this issue Jan 26, 2022 · 2 comments
Closed

A single changelog file instead of two #5728

Pierre-Sassoulas opened this issue Jan 26, 2022 · 2 comments
Labels
Enhancement ✨ Improvement to a component Maintenance Discussion or action around maintaining pylint or the dev workflow
Milestone
2.15.0

Comments

@Pierre-Sassoulas
Copy link
Member

Current problem

We duplicate the changelog in two files. It's burning contributor and maintainer time for no reasons.

Desired solution

One file only (probably the what's new ? markdown) and some automated checks on it. Maybe like the one black does for its own changelog ? Also maybe some consistency check of the old release when removing one of the file.

Additional context

Original idea by @DanielNoord
@Pierre-Sassoulas Pierre-Sassoulas added Enhancement ✨ Improvement to a component Maintenance Discussion or action around maintaining pylint or the dev workflow labels Jan 26, 2022
@Pierre-Sassoulas Pierre-Sassoulas mentioned this issue Jan 26, 2022
Merged
@Pierre-Sassoulas Pierre-Sassoulas mentioned this issue Mar 5, 2022
Merged
@Pierre-Sassoulas Pierre-Sassoulas mentioned this issue Mar 25, 2022
Merged
@Pierre-Sassoulas Pierre-Sassoulas mentioned this issue Apr 11, 2022
Merged
4 tasks
This was referenced May 12, 2022
Merged
Closed
Closed
Merged
Merged
@Pierre-Sassoulas Pierre-Sassoulas mentioned this issue Jun 1, 2022
Closed
8 tasks
@Pierre-Sassoulas Pierre-Sassoulas linked a pull request Jun 8, 2022 that will close this issue
First draft for automatic generation of changelog entries #6875
Closed
9 tasks
@mbyrnepr2
Copy link
Member

I think this has been achieved via #6974. Can we close @Pierre-Sassoulas?

@Pierre-Sassoulas
Copy link
Member Author

Sure, thank you for noticing !

@Pierre-Sassoulas Pierre-Sassoulas closed this as not planned Won't fix, can't repro, duplicate, stale Sep 17, 2022
@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.15.0 milestone Sep 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement ✨ Improvement to a component Maintenance Discussion or action around maintaining pylint or the dev workflow
Projects
None yet
Milestone
2.15.0
2 participants
@Pierre-Sassoulas @mbyrnepr2