-
Notifications
You must be signed in to change notification settings - Fork 15
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
Tag as parameter #10
Comments
Hello @victoraugustolls and thank you for that feature request! There are multiple questions here, so lets split them:
Unfortunately, arguments are used for passing the release artifacts only.
This is true, though I do not think that each action should workaround that but the solution should come from GitHub itself.
Git Tag is required by design as a part of the validation, building current commit and uploading the artifacts, SemVer matching,... I believe if you'd be able to trigger another workflow it will solve all your problems here 😉 P.S: maybe this may help? Although, Release Title manipulation is a good idea and will be implemented in a coming release 🎉 There will be 3 new env.vars to adjust default behavior:
Of course, you might provide both prefix and postfix (name may not be combined with them) to create something like It is possible to pass data between steps inside a workflow using environmental variables inside a workflow. name: release
on:
push:
tags:
- "*"
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v1
- run: |
export TEXT="Release: "
echo "::set-env name=RELEASE_NAME_PREFIX::$TEXT"
- name: Release
uses: docker://antonyurchenko/git-release:latest
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
DRAFT_RELEASE: "false"
PRE_RELEASE: "true"
CHANGELOG_FILE: "CHANGELOG.md"
ALLOW_EMPTY_CHANGELOG: "false"
ALLOW_TAG_PREFIX: "true"
with:
args: |
file1.zip
file2.zip |
Description:
Would it be possible to pass the tag as a parameter? As github actions can't be chained. So if I have an action that create a tag, this tag could be used to read the changelog and create the release.
Also, giving the release name a prefix like:
Release {tag}
would be nice!Reference:
Screenshots:
The text was updated successfully, but these errors were encountered: