You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resolve VERSION against real release tags (try v-prefix and bare),
optional GITHUB_TOKEN/GH_TOKEN for the releases/latest API, defensive
checksum parsing, install/tar preflight, PATH dir normalization, and
README notes. Add a shellcheck job for scripts/install.sh.
Made-with: Cursor
Copy file name to clipboardExpand all lines: README.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,6 +90,8 @@ First-party install script (same idea as [`git-fire/scripts/install.sh`](https:/
90
90
91
91
The `main` URL below always runs the installer script from the latest commit on that branch, while the binary itself comes from the latest GitHub release (or from `VERSION` if you set it). That is convenient for copy-paste installs, but it means the script can drift ahead of any given release. For a fully pinned install, use the release tag in the URL (as in each release’s notes) and set `VERSION` to the same tag.
92
92
93
+
For repeated automation against the GitHub API (resolving `latest`), set **`GITHUB_TOKEN`** or **`GH_TOKEN`** so authenticated rate limits apply. `VERSION` may be a bare semver (`0.9.1`); the installer tries the `v`-prefixed release tag first, then the exact string you passed.
If your shell does not already include `~/.local/bin` on `PATH`, add it (the installer prints a reminder). Example for bash:
105
+
If your shell does not already include `~/.local/bin` on `PATH`, add it (the installer prints a reminder). Example for bash (skips the line if `.local/bin` is already mentioned in `~/.bashrc`):
0 commit comments