Installation

The Pullminder CLI runs on macOS, Linux, and Windows. Choose whichever installation method fits your workflow. All methods produce the same pullminder binary.

Quick install (curl)

The install script detects your OS and architecture, downloads the correct binary, verifies its SHA256 against the published checksums.txt, and places it in $HOME/.local/bin.

curl -fsSL https://get.pullminder.com | sh

If $HOME/.local/bin is not on your PATH, the installer prints the exact lines to add to your ~/.zshrc or ~/.bashrc. You can override the install directory with the INSTALL_DIR environment variable:

curl -fsSL https://get.pullminder.com | INSTALL_DIR=/usr/local/bin sh

You can also pin a specific release with VERSION:

curl -fsSL https://get.pullminder.com | VERSION=0.1.16 sh

Homebrew (macOS and Linux)

brew install pullminder/tap/pullminder

Upgrade to the latest version at any time:

brew upgrade pullminder

npm

If you already have Node.js installed, you can install the CLI as a global npm package:

npm install -g pullminder

Or run it without installing via npx:

npx pullminder check

This is especially useful in CI environments where you want to pin a version in package.json rather than manage a standalone binary.

Manual binary download

Pre-built binaries are published on the GitHub releases page for every supported platform.

Platform	Architecture	Filename
Linux	x86_64	pullminder-linux-amd64
Linux	ARM64	pullminder-linux-arm64
macOS	Intel (x86_64)	pullminder-darwin-amd64
macOS	Apple Silicon	pullminder-darwin-arm64
Windows	x86_64	pullminder-windows-amd64.exe

After downloading, make the binary executable (macOS/Linux) and move it to a directory on your PATH:

chmod +x pullminder-darwin-arm64
sudo mv pullminder-darwin-arm64 /usr/local/bin/pullminder

On Windows, rename the file to pullminder.exe and add the containing folder to your system PATH.

Verify the installation

Run the following command to confirm the CLI is installed and working:

pullminder --version

You should see output like:

pullminder v1.2.0 (abc1234)

Shell completions

Generate completion scripts for your shell:

# Bash
pullminder completion bash > /etc/bash_completion.d/pullminder

# Zsh
pullminder completion zsh > "${fpath[1]}/_pullminder"

# Fish
pullminder completion fish > ~/.config/fish/completions/pullminder.fish

# PowerShell
pullminder completion powershell > pullminder.ps1

After generating the script, restart your shell or source the file to enable tab completions for all commands and flags.

Troubleshooting

pullminder: command not found

The binary was installed but its directory is not on your PATH. The curl installer prints the exact export line to add when this happens; otherwise:

echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc   # zsh
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc  # bash

Restart your shell or source the file. For Homebrew installs the formula already drops the binary in a PATH-managed location, so this only affects the curl path and manual binary downloads.

Error: SHA256 mismatch from the curl installer

The downloaded artifact does not match the SHA256 in the release’s checksums.txt. This usually means the download was corrupted or interrupted. Re-run the install command. If the failure persists, open an issue — do not disable the verification.

macOS Gatekeeper blocks the binary

If you downloaded the binary manually instead of using Homebrew or the install script, macOS may quarantine it. Remove the quarantine attribute:

xattr -d com.apple.quarantine /usr/local/bin/pullminder

Homebrew and the curl installer skip this step automatically.

npm install -g pullminder fails with permissions errors

Global npm installs require write access to the npm prefix. Either run with sudo, configure a per-user prefix (npm config set prefix "$HOME/.npm-global"), or use npx pullminder to skip the install entirely.

Next steps

• Command reference — full list of every command and flag.
• CI integration — run Pullminder in GitHub Actions, GitLab CI, and other pipelines.