Skip to content

Update the release process and setup the process to specify tags - #145

Merged
ZPascal merged 7 commits into
ad-m:masterfrom
ZPascal:update-the-release-process
Mar 10, 2024
Merged

ZPascal merged 7 commits into
ad-m:masterfrom
ZPascal:update-the-release-process

Conversation

@ZPascal

@ZPascal ZPascal commented Nov 7, 2022 •

Copy link
Copy Markdown
Collaborator

The change is related to the following issue.

@ZPascal
ZPascal force-pushed the update-the-release-process branch from 4832d26 to 0fba8e2 Compare November 7, 2022 23:10
@ZPascal
ZPascal requested a review from ad-m November 7, 2022 23:10
@ZPascal ZPascal linked an issue Nov 7, 2022 that may be closed by this pull request
@ZPascal

ZPascal commented Nov 7, 2022

Copy link
Copy Markdown
Collaborator Author

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"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ZPascal

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/[email protected]

It 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.

Copy link
Copy Markdown
Collaborator Author

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.

@ZPascal ZPascal mentioned this pull request Mar 25, 2023
@ZPascal ZPascal self-assigned this Dec 3, 2023
Comment thread .github/workflows/build.yml Resolved
Comment thread .github/workflows/monitoring_link.yml Resolved
Comment thread .github/workflows/publish.yml Resolved
@ZPascal
ZPascal force-pushed the update-the-release-process branch from 0fba8e2 to a2a6943 Compare March 9, 2024 19:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Could you release major version(s) of your GitHub action?

4 participants