You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
#199 introduces a new GitHub workflow for automating LME's release process. The workflow still requires our team to go into the Actions tab and run the workflow manually, since one of the GitHub Actions (action-gh-release) used does not currently support updating an existing draft release.
For additional background here's a few similar issues in the action-gh-release repository where others have had issues updating an existing draft release:
The solution will be the same as the existing build_release.yaml file, except on.pull_request.types should contain opened/synchronize, which will trigger the workflow when a PR prefixed with "release-*" is opened or if commits are added to an existing release PR.
The build-release job is the same, except for some changes in the parameters. Instead of inputs.version we can get the release version programmatically in the Get Release Version step.
Is your feature request related to a problem? Please describe.
#199 introduces a new GitHub workflow for automating LME's release process. The workflow still requires our team to go into the Actions tab and run the workflow manually, since one of the GitHub Actions (action-gh-release) used does not currently support updating an existing draft release.
For additional background here's a few similar issues in the action-gh-release repository where others have had issues updating an existing draft release:
#245
#284
#362
Describe the solution you'd like
The solution will be the same as the existing build_release.yaml file, except
on.pull_request.types
should containopened
/synchronize
, which will trigger the workflow when a PR prefixed with "release-*" is opened or if commits are added to an existing release PR.The build-release job is the same, except for some changes in the parameters. Instead of
inputs.version
we can get the release version programmatically in theGet Release Version
step.The text was updated successfully, but these errors were encountered: