Repository navigation
Create the GitHub release by default on release dispatch - #1337
Conversation
The release job is gated on the create-github-release input, which defaulted to false: a dispatch that left the box unticked built and pushed the images but created no tag and no GitHub release, while still reporting the run as successful. The input is kept, so a build can still be re-run without cutting another release. This also matches the sibling release-warp10.yaml, which already defaults the same input to true. Issue: UTAPI-127
Hello delthas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
|
/approve |
|
!done 2h |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: approve |
Build failedThe build for commit did not succeed in branch w/8.3/improvement/UTAPI-127/default-create-github-release The following options are set: approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
This pull request does not target the following hotfix branch(es) so they
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue UTAPI-127. Goodbye delthas. |
|
|
When creating releases from the manual workflow, we usually want to create the GitHub release.
This flips the default to
truesuch that not pickng anything does the right thing (create the tag and release).That also aligns it with
release-warp10.yaml, which already defaults totrue.Issue: UTAPI-127