#459 Automated release workflow #460
Conversation
| @@ -0,0 +1,12 @@ | |||
| # https://github.com/gradle/wrapper-validation-action#readme | |||
|
|
|||
| name: "Validate Gradle Wrapper" | |||
There was a problem hiding this comment.
Good question, were we going to accept an external PR with a JAR change?
But then did you check the source code of the action to make sure it was not doing anything suspicious it self 😛
There was a problem hiding this comment.
I hope so ! Otherwise we should really contact the Spring Boot team https://github.com/spring-projects/spring-boot/blob/master/.github/workflows/gradle-wrapper-validation.yml !
|
|
||
| name: Release | ||
|
|
||
| on: [ workflow_dispatch ] |
There was a problem hiding this comment.
What about running it once a release is created in GH? So that we don't have to create the release + trigger the job? and triggering the release also means we are more likely to target a branch/tag that is actually a release
There was a problem hiding this comment.
Or maybe we can keep both, upon release and manually
There was a problem hiding this comment.
Yep let me try this way!
There was a problem hiding this comment.
Ticket
#459
Description
Automated release workflow using Github Actions.