-
-
Notifications
You must be signed in to change notification settings - Fork 726
fix: publish nightly draft and title #2358
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes issues with the nightly release configuration by creating a separate GoReleaser configuration file for nightly builds. The main issues addressed are preventing nightly releases from being published as drafts and ensuring correct release titles.
- Created a dedicated
.goreleaser-nightly.yml
configuration file for nightly releases - Removed nightly-specific configuration from the main
.goreleaser.yml
file - Updated GitHub Actions workflows to use appropriate configurations and flags
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
File | Description |
---|---|
.goreleaser.yml |
Removed release draft setting and nightly configuration to clean up main release config |
.goreleaser-nightly.yml |
New dedicated configuration for nightly releases with proper title template and settings |
.github/workflows/release.yml |
Added --draft flag to ensure regular releases are published as drafts |
.github/workflows/release-nightly.yml |
Updated to use the new nightly-specific configuration file |
2782cf2
to
5703aa1
Compare
5703aa1
to
ce5fe81
Compare
bd068b1
to
baef05d
Compare
baef05d
to
c6f30e8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for setting this up!
The nightly release was published as draft
Also the title was incorrect.
I've made the choice use another yaml config to not impact our "real" release workflow