-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: Fixed contributors for bugfix releases #32827
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.
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
DOC: Fixed contributors for bugfix releases #32827
Conversation
Previously we showed just contributors who manually backported commits to the maintenance branch. ``` Contributors ============ A total of 8 people contributed patches to this release. People with a "+" by their names contributed a patch for the first time. * Daniel Saxton * Joris Van den Bossche * MeeseeksMachine * MomIsBestFriend * Pandas Development Team * Simon Hawkins * Tom Augspurger * jbrockmendel ``` Fixed ``` Contributors ============ A total of 22 people contributed patches to this release. People with a "+" by their names contributed a patch for the first time. * Anna Daglis + * Daniel Saxton * Irv Lustig * Jan Škoda + * Joris Van den Bossche * Justin Zheng + * Kaiqi Dong * Kendall Masse + * Marco Gorelli * Matthew Roeschke + * Pedro Reys + * Prakhar Pandey + * Robert de Vries + * Rushabh Vasani + * Simon Hawkins + * Stijn Van Hoey + * Terji Petersen + * Tom Augspurger * William Ayd * alimcmaster1 * gfyoung + * jbrockmendel ```
I guess this will need some more thought. As written, it only works when both the current and previous releases were bugfix releases. I think we'll want to do both approaches (old and new) and then take the union. |
New version (for v1.0.1..v1.0.2)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#31215 was one where the user specifically asked about this, though I don't see them on the list. Any idea what we may be missing there?
# We need two passes over the log for cur and prev, one to get the | ||
# "Co-authored by" commits, which come from backports by the bot, | ||
# and one for regular commits. | ||
xpr = re.compile(r"Co-authored-by: (?P<name>[^<]+) ") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might be responsible for some issues here; I typically clear out all commit messages before squashing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, we'll want to keep it here for backports (GitHub also uses the message I think).
Shouldn't matter for regular PRs, since they use the regular author field, not the message.
I posted the output for 1.0.1..1.0.2, that commit was in 1.0 (but backported during the RC period IIRC). I've confirmed that their name is in the output for v0.25.3..v1.0.0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, thanks for fixing this!
sure. you tagged for 1.04 ? |
Yeah, Joris did. |
So @pandas-dev/pandas-core when you merge PRs made by the backport bot, make sure to keep the text "Co-Authored by ...". Then the original author will be listed in the "Contributors" section of the 1.0.x docs. |
Co-authored-by: Tom Augspurger <[email protected]>
Previously we showed just contributors who manually backported commits
to the maintenance branch.
Fixed
Closes #31717