-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add contributors badges to Github Releases #248
Comments
that's a good suggestion but I wouldn't know how to add this suggested feature, if you know how to please provide a PR |
This is happening automatically as soon as we reference the contributor by name in the changelogs. |
I'm not exactly sure what you mean but the release seems to be created in this file create-release.ts which then calls github-client.ts when the repo is on GitHub. It's getting his info from Octokit, so I don't know if that can pull the contributors but some of these 2 files must be updated to do what you want to do EDIT after looking a bit how the release is created, whatever is displayed in the release actually comes from the conventional-changelog, so for this to work then the changelog creation would have to include the contributor/user and I'm not sure conventional-changelog provides this kind of info (at first glance it doesn't look like it). This git command seems to provide contributor |
it might be doable to change the changelog creation format according to conventional-changelog/git-raw-commits we can provide the $ git log -1 --format='%B (@%cn)' ccbf7bf
chore(release): 4.2.4
(@ghiscoding) the git raw commit is used in the changelog creation here so perhaps that could be changed with the new format option EDIT It seems really hard to add the author to changelog as per this |
@StarpTech you can review the PR #253, it's a bit hacky to circumvent the missing feature from |
Reopening since I just found out that the first code implementation was adding the author's full name (which is what git is holding) instead of the preferable git username which are not the same. It looks like we could use the GitHub API (we can use Octokit) to read commit username. The negative side effect of using GitHub API is that it requires an extra API call but it will also only work with GitHub and it would require completely different implementation for other systems like GitLab, Azure or other enterprise git servers. See this SO for reference Example with GitHub API using a REST call https://api.github.com/repos/ghiscoding/lerna-lite/commits?since=2022-07-01&per_page=5000 it's most probably a lot better to use GraphQL to avoid querying ton of info just to get the user login, see Octokit GraphQL example. Considering all of that, I might actually keep the first implementation but rename the flag to focus on the author's full name and add a second flag that would use the GitHub API. Something along
For GitLab, they also have their GitLab API with commits, however it doesn't seem to include the user name but that can be pulled from users API, perhaps that can be combined with GraphQL |
This is now available in latest release v1.9.0, more info at version#--changelog-include-commits-client-login-msg |
Clear and concise description of the problem
As titled. Example https://github.com/wundergraph/wundergraph/releases/tag/v0.94.0
Suggested solution
See https://github.com/wundergraph/wundergraph/releases/tag/v0.94.0
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: