You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But that's not the Kevin who committed the change :). This user also has a private github email id - ID+USERNAME@users.noreply.github.com. The API documentation states that users having "Public email" listed on their profile can only be searched using email and since there is no public email listed here, search by email id is not useful. Searching by names as seen below can result in unexpected results.
From the discussion -
Lookup should -
check email, if private then extract username. done.
search by email. If found use name.
use name as extracted from commit message (this would need to be recorded as well. I think only the email is recorded at the moment.
The text was updated successfully, but these errors were encountered:
The ChangelogGenerator.User class assumes the resolved user has an URL. But this may not be the case when the returned username is from a private email nor when the plain name is returned.
Discussed in #1111
Task List
Steps to Reproduce
Find a user who -
If that user has a commit on the repo, observe his entry in the change log.
Expected Behaviour
When generating the changelog, the contributor's correct username is added.
Actual Behaviour
Looks like it is searching by Author's name - 'Kevin King' (see web query here) and just picked up the first user found
https://github.com/jreleaser/jreleaser/blob/main/sdks/jreleaser-github-java-sdk/src/main/java/org/jreleaser/sdk/github/XGithub.java#L103-L111 -
But that's not the Kevin who committed the change :). This user also has a private github email id - ID+USERNAME@users.noreply.github.com. The API documentation states that users having "Public email" listed on their profile can only be searched using email and since there is no public email listed here, search by email id is not useful. Searching by names as seen below can result in unexpected results.
From the discussion -
Lookup should -
The text was updated successfully, but these errors were encountered: