@ghuntley yes, I like this idea. If you have a look at this blog post:

http://cakebuild.net/blog/2016/09/cake-v0-16-0-released

I have some working code to generate the list of contributors that you can see there. Adding that to an item in the release notes is "harder". An issue might have been created by one person, and fixed by another via a pull request. Stitching the two together is where it becomes hard. Not impossible, just not sure how much effort it will take.

The list of contributors is very simple to generate.

List of contributors, with a hyperlink to commits by author would suffice imho.

@ghuntley yes, that sounds doable 😄

Some other ideas which are kinda glamourous :)

https://twitter.com/RobertWPearce/status/910978463586074625

Why have a hyperlink when you can put someone's avatar in the release notes?

Two things to keep in mind:

• milestone can contain issues as well as PRs
• Issues may or may not be linked to a PR and, similarly, PRs may or may not be linked to an issue

In my opinion, the ultimate solution for this feature would be something like this:

1. Properly attribute each issue/PR and also display info about the linked issue/PR if possible. Like so:

   1. When issue is not linked to a PR: [#xxx](<issue URL>) <title of the issue> raised by [<author or the issue>](<issue author's GitHub profile URL>)
   2. When issue is linked to a PR: [#xxxx](<issue URL>) <title of the issue> raised by [<author or the issue>](<issue author's GitHub profile URL>) resolved in [#zzz](<PR URL>) by [<author or the PR>](<PR author's GitHub profile URL>)
   3. When PR is not linked to an issue: [#xxx](<PR URL>) <title of the PR> by [<author or the PR>](<PR author's GitHub profile URL>)
   4. When PR is linked to an issue: [#xxxx](<PR URL>) <title of the PR> by [<author or the PR>](<PR author's GitHub profile URL>) raised in [#zzz](<issue URL>) by [<author or the issue>](<issue author's GitHub profile URL>)

2. Contributors summary
   Display a summary of all the users who contributed to the release. Something similar to this:
   
   This screenshot was taken from the Octokit.net release notes here

I'm currently working on a proof of concept. If I'm successful I'll be happy to contribute a PR to implement this new feature.

This would be a great addition!

Determining if an issue is linked to a PR (and vice-versa) is turning out to be much more difficult than I anticipated because the Github API does not return this info when an issue is retrieved. I did a lot of research and I found people offering two possible solutions:

1. retrieve the events in the issue "timeline", attempt to figure out which even corresponds to "issue was linked to PR", and finally try to figure which issue/PR is being referenced
2. parse the HTML from Github's web site for this particular issue and search an element with a specific CSS class name. If this element contains an anchor, the "href" property of this anchor will reveal the unique identifier of the issue/PR in question

The first option would be my preferred solution but, as I explained in this comment, I hit a dead end.

The second option (presented here) is very brittle since it relies on the presence of a HTML node with a specific CSS class. This can change at any moment if Github decides to make changes to their UI.

Maybe there's a third possible solution: use a GraphQL query to retrieve the desired data. I haven't explored Github GraphQL API, so this will be a learning experience for me. I'll spend some time researching/learning and report my findings.

Status update
I am able to figure out the linked issue/PR using a GraphQL query and I can generate release notes like this:

In the above example, the two highlighted issues have a linked PR. This works great in most cases!

However I discovered that in some case, for a reason I can't explain, the Github GraphQL API returns an empty array of events when fetching the timeline for a given issue which, obviously, prevents my logic from determining the given issue has a linked PR.

Status update
I am also able to generate a summary of people who made a contribution towards the release (meaning they either raised an issue or submitted a PR):

I didn't realize until yesterday that a single PR could be linked to more than one issue like in this example:

This also applies to issues: they can be linked to more than one PR.

I need to update my PR to account for this possibility.

Also, GitReleaseManager was recently updated to support GitLab in addition to GitHub. I need to modify my PR to also support GitLab.