HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
paulirish
git-open
Shell2015–2022
paulirish / git-open

git-open

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

7Distinct people
9Mentions
2Explicit recommenders
3.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

I use git-open [1] for this – highly recommended. It supports multiple remotes and works great with custom hosted servers out of the box. [1]: https://github.com/paulirish/git-open

hugolundin used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year9 dated mentions

Observed mentions: 2015-02-03 17:30:34 UTC to 2022-08-21 09:56:04 UTC.

01232015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC321
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202

What Hacker News says

9 sources
That's right, and for GitLab `glab mr view -w` will work. I wanted to have a tool that works with both and lets you open in browser whatever you're currently looking at. So it opens the PR for current branch, repository home page for main branch and PR creation page for new branch. You can also open the repository with `git open` [1], and create a PR clicking the link you see after pushing to GitHub/GitLab, but the goal was to have all three in a single command. [1]: https://github.com/paulirish/git-open
In Show HN: Open current Pull Request in browser with a single command
Waterluvian·Dec 26, 2020Recommendation phrase
I love git open[0] but I was always a bit mystified by how a simple "npm install" command can modify what it needs to in order for "git open" to become a valid command. It's convenient but, in my opinion, at a cost of "magic" being done to my machine with a "don't worry about it" attitude. A UX I could get down with would be "npx run git-open" followed by a short CLI that tells me what it's about to do, why, and asks for confirmation. [0]https://github.com/paulirish/git-open
In Getting rid of NPM scripts
[I'm the author of diff-so-fancy, Steve helped with shipping it as a standalone script] NPM?!? :) A lot of people below are asking why a bash script (that depends on a perl script) is being recommended to install via NPM? The short reason is that NPM is the most straightforward way to get a script installed as a global binary in a cross-platform manner. This approach has worked quite well with `git-open`[0]. Asking all users to deal with the PATH is not my ideal. In addition, I wanted a reasonable upgrade path, in case there are neccessary bugfixes. It's not a great experience if users identify bugs but the fix means they manually find it/download/PATH-ify each time. :/ That said, I'll add some Manual Install instructions to the readme so it's clear how to do this on your own. :) ( Edit: Here they are… https://github.com/stevemao/diff-so-
Read the rest
In Diff So Fancy: make Git diffs look good
Made this little jobby last night after stumbling across this: https://github.com/paulirish/git-open which is also awesome. Launch the homepage: gem home gem-name View Issue tracker: gem issues gem-name View Documentation: gem docs gem-name It tries to do some clever stuff like falling back to github url's if the gem creator didn't add explicit links. Falls back to rubydocs if there are no links and the gem isn't hosted on github. To Install: gem install gem-home
In Gem command extensions for launching a gem's homepage, issues and documentation

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.