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
The new release script introduced in #1078 generates a changelog without the link to the author github profile:
dependabot alert 21 about Django (on tests) (#1067). By Bruno Rocha.
Proposal
I want it to be rendered as:
dependabot alert 21 about Django (on tests) (#1067). By [Bruno Rocha](https://github.com/rochacbruno).
Additional Context
The reason the github link is not fetched is because git-changelog only uses information available in git (name and email) in the commit range to be released.
To fetch the github link, we could hit the github API:
Fetch a list of users from latest release to the current one
Map user-email: url
Link git user.email with github url using that map
We may have to open a PR in git-changelog to support this. Possible approaches to present to the project:
add the GitHub API fetch inside git-changelog
make it possible to provide a map (user-email: url), which should be available internally the template.
This map could be a simple toml file
We should generate this file externally using the GH API.
Possibly, we could integrate that solution with fixing the update_contributors workflow, which is broken.
The text was updated successfully, but these errors were encountered:
Problem
The new release script introduced in #1078 generates a changelog without the link to the author github profile:
Proposal
I want it to be rendered as:
Additional Context
The reason the github link is not fetched is because
git-changelog
only uses information available in git (name and email) in the commit range to be released.To fetch the github link, we could hit the github API:
user-email: url
user.email
withgithub url
using that mapWe may have to open a PR in
git-changelog
to support this. Possible approaches to present to the project:user-email: url
), which should be available internally the template.Possibly, we could integrate that solution with fixing the
update_contributors
workflow, which is broken.The text was updated successfully, but these errors were encountered: