-
Notifications
You must be signed in to change notification settings - Fork 233
Update the release process and setup the process to specify tags #145
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
4832d26 to
0fba8e2
Compare
|
Hi @jackton1, could you please review the PR? |
| - name: Setup the release version and overwrite the existing major version tag | ||
| run: | | ||
| major_version=$(echo $GITHUB_REF_NAME | cut -d. -f1) | ||
| git config --local user.email "github-actions[bot]@users.noreply.github.com" |
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.
By the way: there is also a GitHub Action to take care for exactly this setup of the GitHub Actions bot. You can call it as follows:
- name: user
uses: fregante/setup-git-user@v1.1.0It needs to have access to the file contents, i.e. it requires a preceding actions/checkout call and at least permissions.contents: read in the permissions section. Also large organisations like Adobe and Ansible make use of this Action; see https://github.com/fregante/setup-git-user/network/dependents (page 2, as of this writing) for reference.
Maybe this could help to enhance the maintainability of this workflow.
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.
@kevinmatthes Thanks for the hint. I'll check that.
0fba8e2 to
a2a6943
Compare
The change is related to the following issue.