finds.dev← search

// the find

paulirish/git-open

★ 3,445 · Shell · MIT · updated May 2026

Type `git open` to open the GitHub page or website for a repository in your browser.

A shell script that adds a `git open` subcommand to jump straight to the GitHub/GitLab/Bitbucket page for the current repo or branch in your browser. Single-file, zero-dependency, does exactly one thing. For developers who find themselves manually copy-pasting repo URLs more than once a day.

The --issue flag parses branch names like `issue/123` or `fix/#456` and opens the corresponding issue directly — that's a genuinely useful convention. Support for named remotes and arbitrary branches as arguments makes it useful on forks where origin isn't the upstream. The --suffix flag is an escape hatch that keeps the tool extensible without adding flags for every GitHub sub-page (PRs, actions, etc). BATS test suite exists and covers the URL-construction logic, which is the part most likely to break when providers change their URL formats.

Windows support is a second-class citizen — the PowerShell workaround in the README requires manually hardcoding the bash path, which breaks on non-default Git installs. The --issue flag only works with GitHub, VSTS, and TFS; GitLab and Bitbucket users get silent fallback to the branch page with no warning. The changelog stops at 2018 and the last real release was v2.1.0 the same year, so the repo is essentially in maintenance mode — fine for a stable tool, but new providers (Forgejo, Gitea, Codeberg) won't be added anytime soon. The npm install path exists purely for PATH convenience and pulls in no actual Node dependencies, which is a weird indirection that confuses people expecting a Node package.

View on GitHub →

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →