Skip to content

Conversation

lucyleeow
Copy link
Member

Reference Issues/PRs

ref: #32081 (comment)

What does this implement/fix? Explain your changes.

Add note that changelog entries should be a single bullet point

Any other comments?

@lucyleeow lucyleeow added the Quick Review For PRs that are quick to review label Sep 3, 2025
@@ -22,7 +22,8 @@ This file needs to be added to the right folder like `sklearn.linear_model` or
`sklearn.tree` depending on which part of scikit-learn your PR changes. There
are also a few folders for some topics like `array-api`, `metadata-routing` or `security`.

In almost all cases, your fragment should be formatted as a bullet point.
In almost all cases, your fragment should be formatted as a **single** bullet point.
Note the aggregation software cannot handle more than one bullet point per entry.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure that this second line is necessary. Maybe just adding 'single' above is adequate?

Copy link
Member

@lesteve lesteve Sep 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it's not entirely accurate (but probably good enough for now 😉), you can probably do a top-level bullet point and some nested bullet points if you really want (not sure it's a good idea, the changelog is already long enough ...).

I guess the thing to maybe do more is to have a look at the PR rendered doc and check that the changelog looks OK. Not super convenient to get to but it's there somewhere e.g. for this PR: https://output.circle-artifacts.com/output/job/e7181091-4ac6-4397-8fc7-c9c9f3f73475/artifacts/0/doc/whats_new/v1.8.html

Maybe it would be worth adding a changelog link to _changed.html ...
image

Copy link
Member

@lesteve lesteve Sep 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it would be worth adding a changelog link to _changed.html ...

Actually I double-checked and the functionality is already there. For example #31564, rendered doc shows a link to the changelog (because a file was added in doc/whats_new/upcoming_changes:
image

So I guess it is mostly a matter of remembering to double-check the rendering of the changelog.

@lucyleeow
Copy link
Member Author

cc @ogrisel

Copy link

github-actions bot commented Sep 3, 2025

✔️ Linting Passed

All linting checks passed. Your pull request is in excellent shape! ☀️

Generated for commit: f8effed. Link to the linter CI: here

@ogrisel ogrisel merged commit 6488763 into scikit-learn:main Sep 3, 2025
43 checks passed
@lucyleeow lucyleeow deleted the single_bullet branch September 3, 2025 10:42
@jeremiedbb jeremiedbb mentioned this pull request Sep 3, 2025
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Quick Review For PRs that are quick to review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants