Skip to content

Add workflow to auto update Homebrew Casks#411

Merged
mjcheetham merged 1 commit intomicrosoft:mainfrom
mjcheetham:homebrew-release
Jul 24, 2020
Merged

Add workflow to auto update Homebrew Casks#411
mjcheetham merged 1 commit intomicrosoft:mainfrom
mjcheetham:homebrew-release

Conversation

@mjcheetham
Copy link
Member

Add a GitHub workflow that is triggered on creation and publish of a release on GitHub, to update the scalar and scalar-azrepos Casks on the microsoft/git Homebrew Tap.

Add a GitHub workflow that is triggered on creation and publish of a
release on GitHub, to update the `scalar` and `scalar-azrepos` Casks on
the microsoft/git Homebrew Tap.
type: cask
version: ${{ steps.version.outputs.result }}
sha256: ${{ steps.hash.outputs.result }}
alwaysUsePullRequest: true
Copy link
Member Author

Choose a reason for hiding this comment

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

Similarly to the GCM Core workflow, we always create PRs rather than push a commit immediately to give us one more 'gate'.

- name: Update scalar-azrepos Cask
uses: mjcheetham/update-homebrew@v1.1
with:
token: ${{ secrets.HOMEBREW_TOKEN }}
Copy link
Member Author

Choose a reason for hiding this comment

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

This token is a PAT (mine) has been added to the repository. The commits/PRs will be created as 'me'.
Would be nice if we had a 'service user' who we could use instead.

with:
asset: Installers_macOS_Release.zip
hash: sha256
token: ${{ secrets.GITHUB_TOKEN }}
Copy link
Member Author

Choose a reason for hiding this comment

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

This token is automatically created. It only has public read access to GitHub repos, which is all we need to compute the hash from a released Scalar asset.

@mjcheetham mjcheetham merged commit 44869ce into microsoft:main Jul 24, 2020
@mjcheetham mjcheetham deleted the homebrew-release branch July 24, 2020 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants