tri/homebrew-tap
1
0 Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

ci: run the bump workflow on Gitea Actions

Browse Source 
The tap moved to git.trivk.dev. Gitea Runner has no parallel steps, so
the two bumps run one after the other. The scripts ask api.github.com
with curl instead of gh, which needs a GitHub token the Gitea job does
not have; two unauthenticated requests per run stay far under the limit.
The README now taps with the git.trivk.dev URL.
This commit is contained in:
tri committed 2026-11-10 15:53:28 +07:00
1 parent a573d6948f
commit 07026e2c7a
4 files changed
+17 -16
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

README.md
+6 -3
View File
@@ -11,15 +11,18 @@ My personal Homebrew tap for macOS.
## Install
```sh
brew tap vokhactri/tap
brew tap vokhactri/tap https://git.trivk.dev/tri/homebrew-tap.git
brew trust vokhactri/tap
brew install vokhactri/tap/<name>
```
Use `brew install --cask` for casks.
The tap lives on git.trivk.dev, so `brew tap` needs the URL. Without it, Homebrew looks on GitHub,
where the old copy is archived and no longer updated.
## Updates
A GitHub Action checks for new upstream releases every two hours and commits the new version
and sha256 values. If a release doesn't have its macOS files yet, the Action tries again on the
A Gitea Actions workflow checks for new upstream releases every two hours and commits the new
version and sha256 values. If a release doesn't have its macOS files yet, the Action tries again on the
next run.