[Repo Assist] ci: automatically create GitHub releases on push to main#1750
Closed
[Repo Assist] ci: automatically create GitHub releases on push to main#1750
Conversation
When a new version is merged to main, after NuGet publish, check whether a GitHub release already exists for the version read from RELEASE_NOTES.md. If not, extract the release notes for that version and create a tagged release attaching the built NuGet packages. This uses the GITHUB_TOKEN (permissions: contents: write is already set for gh-pages deployment) and the pre-installed gh CLI on windows-latest runners. Addresses #1742 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Apr 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a new version is merged to main, after NuGet publish,
check whether a GitHub release already exists for the version
read from RELEASE_NOTES.md. If not, extract the release notes
for that version and create a tagged release attaching the
built NuGet packages.
This uses the GITHUB_TOKEN (permissions: contents: write is
already set for gh-pages deployment) and the pre-installed
gh CLI on windows-latest runners.
Addresses #1742
Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com