4 ms·
I browse repos on github pretty frequently. Some use cases: - It's someone else's repo (eg, a gem I'm using), and I just want to see one line real quick, rath
by fishtoaster 12y ago
I browse repos on github pretty frequently. Some use cases:
- It's someone else's repo (eg, a gem I'm using), and I just want to see one line real quick, rather than cloning the whole project locally and finding it there.
- It's my repo, but I my local working copy is on a different branch or has uncommitted changes, so I don't want to bother stashing + changing branches just to look up one line
- I'm poking around several repos that I have no intention of using- eg, looking at an interview candidate's public repos
- staticshock 12y agoFor the "my repo, wrong branch" use case, you have some options: git show other-branch:path/to/file or: git grep -e pattern other-branch
- skyebook 12y agogit-grep is indescribably awesome. To be fair though, I search github pretty frequently because it means I can search issues also. If issues were git repos themselves it would be a different ballgame.