Github Automated Release Notes

[cporten522]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

I can't find an article related to this solution

What changes are you suggesting?

I would like to propose that GitHub's automated release notes should go a bit deeper into each PR's changes, and then use AI with a specified system prompt to read all Changes, and spit them out in a digestible release notes format. Right now, we get the commit comment and who did it, but that is not enough.

In reality, the developer may not give a great commit description that encompasses all that was changed. Their code may be great, and the AI should be able to understand these changes and describe how they affect the end user. I have tested this within the Changes and used CoPilot to do just this, and it worked great. But very manual.

Additional information

No response

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[Sharra-writes]

@cporten522 Thanks for opening an issue! To clarify, are you talking about GitHub better summarizing its own release notes for product updates, or are you asking for a new feature that anyone can use in their own repository? I ask because I'm not certain the docs team is responsible for release notes at all (I can ask how much we're involved), but I know we can't do anything for feature requests. If it's the latter, I suspect support will be the ones you need to talk to, but I can check and see if there's a better route for a suggestion like that.

[cporten522]

Not GitHub's product release notes. But building upon the feature that Github already has for users. I think there is massive room for improvement here. When I want to put together a release, CoPilot should be able to summarize the Changes that were made and prepare them for product updates for me!

[Sharra-writes]

@cporten522 Thanks for clarifying! That's definitely not something the docs team can help with, since it's an engineering task, and this is the repository for the docs team. But let me see if I can find you a more direct avenue than support, even though I suspect support is going to be the go-to.

[Sharra-writes]

@cporten522 Okay, we have a place specifically for feedback: https://github.com/github/feedback/discussions 💛

I'm going to close this one since we can't help with it here, but I hope you get the feature upgrade you're looking for. Seems like it would be useful for everyone.