Repository navigation
feat(release): auto-pr to tap repo - #26
Merged
Merged
Conversation
defaultdino
reviewed
Oct 16, 2026
defaultdino
left a comment
defaultdino
left a comment
Owner
There was a problem hiding this comment.
correct me if I am wrong but this requires a new secret to be created, no?
Collaborator
Author
|
yes, you would need to setup a token in the tap repo that has PR rights (or write rights if you want the auto-push), which we would then include in this repo's env vars |
Owner
|
@BlieNuckel Rebase it with main and I can approve it. I have added the necessary secrets and env variables |
BlieNuckel
force-pushed
the
feat/auto-release-mac
branch
from
October 29, 2026 19:03
d436185 to
f3b742c
Compare
defaultdino
approved these changes
Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a gh action to automatically open a PR against homebrew-tap repo with the new SHA whenever there's a release tag attached to the commit.
Depending on how we want to handle tokens, this could probably be made even better with a direct push on the main branch of the homebrew-tap repo