Skip to content
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

[enhancement]: GitHubRelease@1 should have option to auto generate release notes #20759

Open
VictorIreri opened this issue Jan 1, 2025 · 0 comments

Comments

@VictorIreri
Copy link

VictorIreri commented Jan 1, 2025

Task name

GitHubRelease@1

Describe your feature request here

The GitHub API provides a generate_release_notes parameter but the GitHubRelease@1 task does not provide this functionality.
Image

Currently, release notes are provided via the inputs releaseNotesSource (with value filePath or inline) and either releaseNotesFilePath or releaseNotesInline. Perhaps the releaseNotesSource input could support an additional value auto, which would provide the new functionality without breaking existing setups.

I also tried using changeLogType: issueBased, which is the task's own implementation of automatically generating release notes but faced issues. The docs state it would list all the issues or pull requests included in the release however, I got the error below presumably because the logic in Changelog.ts doesn't account for commits with Azure work item number formatting such as AB#1011069 and so it tried to find GitHub Issue/PR #1011069, which doesn't exist.

Error fetching issues. Cannot generate change log.
##[warning][{"type":"NOT_FOUND","path":["repository","_1011069"],"locations":[{"line":3,"column":193}],
"message":"Could not resolve to an issue or pull request with the number of 1011069."}]

So I'm suggesting the option to use GitHub's logic instead.
FYI, automatic release note generation is also available in GitHub CLI and GitHub's UI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant