feat(signature): parse username from GitHub noreply email#83
Merged
Conversation
Developers who use GitHub's privacy email commit with
{id}+{username}@users.noreply.github.com. The existing email search API
returns nothing for these addresses, so the signature check would fail
with "author not found" even for local pre-commit hooks where the Commits
API is also unavailable (commit not yet pushed).
Parsing the username directly from the noreply address requires no API
call and covers the common privacy-email case. Runs after the Commits API
step and before the email search fallback.
Signed-off-by: Nerijus Bendžiūnas <nerijus.bendziunas@gmail.com>
Coverage Report (Δ +0.0%)
|
||||||||||||||||||||
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.
Developers who use GitHub's privacy email commit with
{id}+{username}@users.noreply.github.com. The existing email search API
returns nothing for these addresses, so the signature check would fail
with "author not found" even for local pre-commit hooks where the Commits
API is also unavailable (commit not yet pushed).
Parsing the username directly from the noreply address requires no API
call and covers the common privacy-email case. Runs after the Commits API
step and before the email search fallback.