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

fixup! homebrew: add GitHub workflow to release Cask #510

Merged
merged 1 commit into from
May 31, 2022

Conversation

derrickstolee
Copy link
Collaborator

We initially used pull requests for the Homebrew releases as a manual
step to ensure that the automation didn't do anything too problematic.
However, we are now manually approving something that has never failed.
Let's just push directly to the branch, if possible, reducing the manual
steps involved in the release process.

We initially used pull requests for the Homebrew releases as a manual
step to ensure that the automation didn't do anything too problematic.
However, we are now manually approving something that has never failed.
Let's just push directly to the branch, if possible, reducing the manual
steps involved in the release process.

Signed-off-by: Derrick Stolee <derrickstolee@github.com>
@derrickstolee derrickstolee self-assigned this May 31, 2022
Copy link
Member

@mjcheetham mjcheetham left a comment

Choose a reason for hiding this comment

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

Looks good to me! As long as the user whose credentials the workflow runs with has permissions to push commits to the master branch in the Tap, this should work ok!

I believe that user would be me and I am an admin of the Tap repo in question, so should be good(!)

@derrickstolee derrickstolee merged commit 2ed6b9a into microsoft:vfs-2.36.1 May 31, 2022
@derrickstolee derrickstolee deleted the brew-immediate branch May 31, 2022 20:54
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.

2 participants