Skip to content

chore: migrate Homebrew install to unified gfargo/tap#85

Merged
gfargo merged 1 commit into
mainfrom
feat/unify-homebrew-tap
Jun 13, 2026
Merged

chore: migrate Homebrew install to unified gfargo/tap#85
gfargo merged 1 commit into
mainfrom
feat/unify-homebrew-tap

Conversation

@gfargo

@gfargo gfargo commented Jun 13, 2026

Copy link
Copy Markdown
Owner

Migrates localpress's Homebrew install to the shared gfargo/homebrew-tap tap, part of unifying all gfargo formulae under one tap (gfargo/homebrew-localpress#1).

- brew install gfargo/localpress/localpress
+ brew install gfargo/tap/localpress

Changes

  • Formula/localpress.rb — header comment points at the shared tap + new install command.
  • README.md — Homebrew badge links to gfargo/homebrew-tap; install command updated.
  • docs/blog-post-v2.md — install snippet updated.
  • .github/workflows/release.yml — the formula-push step now clones/pushes to gfargo/homebrew-tap (formula build / release-asset logic unchanged).

The formula already lives in the shared tap (gfargo/homebrew-tap/Formula/localpress.rb, ported from the old tap at v2.0.0).

⚠️ Action required after merge

The HOMEBREW_TAP_TOKEN secret on this repo must grant repo scope on gfargo/homebrew-tap (previously gfargo/homebrew-localpress) so the release workflow can push formula updates.

Point all Homebrew references at the shared gfargo tap
(gfargo/homebrew-tap) instead of the per-project gfargo/homebrew-localpress
repo, dropping the repeated formula name:

    brew install gfargo/tap/localpress   # was: gfargo/localpress/localpress

- Formula header comment + README badge/install command
- blog-post-v2 install snippet
- release workflow now pushes the formula to gfargo/homebrew-tap

Note: the HOMEBREW_TAP_TOKEN secret must grant repo scope on
gfargo/homebrew-tap for the release push step.
@gfargo gfargo merged commit 71a9369 into main Jun 13, 2026
4 checks passed
@gfargo gfargo deleted the feat/unify-homebrew-tap branch June 13, 2026 16:57
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.

1 participant