This repository was archived by the owner on May 21, 2026. It is now read-only.
Dumb-tap refactor: remove in-tap automation#3
Merged
Conversation
The release pipeline in stackhawk/hawkop now owns rendering and pushing of Formula/*.rb, mirroring how stackhawk/hawkscan's build.gradle.kts drives stackhawk/homebrew-cli via JGit. This tap becomes a passive destination — just Formula/*.rb files plus a README. Removed: - .github/workflows/update-formula.yml and test.yml — the release runs in the hawkop repo, so there's nothing for this repo's CI to gate on. - scripts/formula-template.rb — the template lives upstream at stackhawk/hawkop:brew/hawkop.rb.template. - scripts/update-formula.sh and its bats tests — the gradle task in hawkop handles rendering directly. Rewrote README to describe the maintenance model and the pinned-version install syntax (hawkop@X.Y.Z). Formula/hawkop.rb lands here when hawkop v0.6.2 (or later) releases.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Summary
Mirrors the
stackhawk/homebrew-clipattern. That tap has no workflows,no scripts — just
hawk.rb,hawk@X.Y.Z.rbfiles, and a README. Allcommits come from
runnerwith messages like "Updating brew's hawk.rbto version 5.5.0", pushed directly by the
releaseCliBrewFormulagradle task in
stackhawk/hawkscan:build.gradle.kts.This PR aligns
homebrew-hawkopwith that model:.github/workflows/update-formula.ymlandtest.yml— removed.The release runs in the producer repo, not here.
scripts/formula-template.rb— removed. The template alreadylives at
stackhawk/hawkop:brew/hawkop.rb.template; the gradle taskreads from there.
scripts/update-formula.shandscripts/test-update-formula.bats—removed. Rendering happens in the gradle task.
README.md— rewritten to describe the maintenance model and thepinned-version install syntax (
hawkop@X.Y.Z).Net: -402 lines of automation that were solving the wrong problem.
Why the revert
PR #1 built an in-tap workflow triggered by
workflow_dispatch/repository_dispatch. That's a reasonable pattern but not the oneStackHawk already standardized on. Moving to the hawkscan pattern means
one fewer auth boundary (no cross-repo token needed) and one rendering
code path instead of two.
What lands in this tap after this merges
Nothing — just this cleanup.
Formula/hawkop.rbgets pushed by thefirst
stackhawk/hawkopprod release that has the new gradle taskwired up. That's a follow-up PR in
stackhawk/hawkop.Test plan
brew untap stackhawk/hawkop; brew tap stackhawk/hawkop— tap should clone cleanly even with no formula present (users will
just get "No available formula" until the first release lands it,
which matches reality).
stackhawk/hawkopand a prod release,brew install stackhawk/hawkop/hawkopworks end-to-end.