Handle temporary new bors e-mail #88
Merged
Conversation
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
Kobzol
force-pushed
the
generalize-bors-reviewer
branch
from
a098824 to
5a0c07e
Compare
31 tasks
Mark-Simulacrum
approved these changes
Jan 14, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
To attribute the 28 contributions (https://thanks.rust-lang.org/rust/all-time/) from
rust-bors[bot]tobors:) An alternative would be to add the temporary bors e-mail address to.mailmapand then usecommit.author_with_mailmap(...), but that sounds more complicated and could hide the temporary e-mail address ingit log, in case someone was debugging it.For context, new bors was using this username for ~5 days between 7. 1. and 12. 1. 2026.