Skip to content
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

feat: convenience workflow for update major release tag #28

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

oliver-butterley
Copy link
Contributor

Adds a workflow which can be called manually (workflow_dispatch) and gives a convenient way to update the major tag to point to the latest release (or roll back to a previous release if required).

@oliver-butterley
Copy link
Contributor Author

I didn't find a way to automate the major tag update without a considerable amount of work or relying on an action we are recommended not to use.

This is a convenience workflow that does nothing more that gives an easy interface for updating the tag so this task can be done without thinking about git commands and is guaranteed to be the same style each time.

I tested it to work in another repo and it does fine. Moreover it does very little so no risk of bad things.

Feel free to just ignore this PR if you prefer another approach, this is very much a style thing.

- name: Git config
run: |
git config user.name "github-actions[bot]"
git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
Copy link
Collaborator

@austinletson austinletson May 18, 2024

Choose a reason for hiding this comment

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

Do you have a link to a doc which explains how this github actions bot user works?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I wish there was something in the docs about this! I failed to find anything relevant. The best I can suggest is the conversation on this PR for actions/checkout.

I suspect we can set anything as the git user and the tagging still works, I believe the choice is just to get the correct image when commits are view on gh webpages.

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.

None yet

2 participants