Merged
Conversation
* Related to release management described in gh-1. * This patch adds a small script to automatically generate the list of authors that contributed to a given release of our project (I've shamelessly borrowed the script from license-compatible SciPy, where I also do releases...). * We may expect the CI to fail here temporarily for the same reason noted at: #17 (comment)
tylerjereddy
commented
Jan 31, 2026
| # This file is up-to-date if the command git log --format="%aN <%aE>" | sort -u | ||
| # does not list the same person multiple times. | ||
| # | ||
| Emma Viani <eiviani@lanl.gov> eiviani-lanl <eiviani@lanl.gov> |
Collaborator
Author
There was a problem hiding this comment.
If we don't add this then the author list will list Emma twice as shown below. That's the point of the .mailmap, to simplify the scenarios where folks contribute from multiple machines or have different aliases, etc.
Authors
=======
* eiviani-lanl (8) +
* Navamita Ray (40)
* Tyler Reddy (66) +
* Emma Viani (56) +
A total of 4 people contributed to this release.
People with a "+" by their names contributed a patch for the first time.
This list of names is automatically generated, and may not be fully complete.
NOTE: Check this list manually! It is automatically generated and some names
may be missing.
* Ignore the `tools/authors.py` script in the `ruff` configuration because this module is vendored from SciPy.
d8ac3b2 to
0be76cb
Compare
tylerjereddy
commented
Jan 31, 2026
| line-length = 88 | ||
| extend-exclude = [ | ||
| "tools/authors.py", # vendored from SciPy | ||
| ] |
Collaborator
Author
There was a problem hiding this comment.
I've excluded this module from the linting because it is vendored from another project, which allows the CI to pass here.
If reviewers prefer it linted I can do that too, it may just make re-vendoring more annoying in the future if there are upstream changes.
Collaborator
Author
|
I'll probably expect folks to start helping me with simple merge conflicts as well, because there are going to be a lot in the leadup to the release. |
nray
approved these changes
Feb 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to release management described in MAINT, ENH: library code/manuscript tracking #1.
This patch adds a small script to automatically generate the list of authors that contributed to a given release of our project (I've shamelessly borrowed the script from license-compatible SciPy, where I also do releases...).
We may expect the CI to fail here temporarily for the same reason noted at:
DOC, MAINT: tools script for release notes lists #17 (comment)
Here's a sample of what running the authors script at the moment produces:
python tools/authors.py cd5f6b0732f59..0cfcf3ef443acwhich shows the authors and their commit counts: