1. 30

  2. 7

    This is niiiiiice.

    I read a lot of code everyday and I don’t want to clone every single repo I poke into. I hope Github takes some UI/UX ideas from this.

    Being able to bounce between different files in the same namespace in a Haskell library without bouncing “out” of the file into the directory and then clicking “into” a different file and instead going directly to the file I want from the side panel is great.

    1. 5

      Github’s keyboard shortcuts can help here, hit t and start typing the name of the file you want to browse to.

      Of course, that’s predicated on knowing the filename you want to view, but when you do it’s a real click-saver

      1. 4

        I use vimium, there’s a conflict there.

        1. 2

          To view all of GitHub’s shortcut keys, press ?, then click the ‘Show All’ link. They are quite similar to those GMail uses for searching and navigation.

          Some other useful shortcuts:

          • l to jump to a line
          • w switch branch/tag
          • / search current repo
          1. 1

            Github became so much more useful once I discovered the t shortcut. When asked questions at work about certain parts of our codebase I now refer to the Github repository to search for a file rather than my possibly stale local copy of the same project. It makes quick references very accessible.

        2. 3

          I’d love to install this, and I’d probably use it every day, but I still can’t bring myself to trust random 3rd party extensions/apps with something as sensitive as the private repos I have access to on GitHub.

          I say that as someone who only accesses GitHub through a dedicated browser though, so maybe I’m just one of those paranoid people =)

          1. 1

            I decided to trust, balance tilted by the extension only requesting access to “github.com”, not the open Internet. There is an exfiltration path: post to a new Gist in an attacker-controlled account. But it’s only one path and if it’s used, then logs at GitHub should identify it happening and quickly lead to us discovering malice as the extension gets blacklisted.

            So it’s in a far better shape than most other options and I decided to go ahead. The tokens I generate don’t include gist access, though – I was careful to uncheck that. I don’t normally have multi-file gists with enough files to need tree views to examine them and I do sometimes have slightly sensitive data in secret gists.

          2. 2

            I also use octosplit to get side-by-side code diffs.

            1. 2

              Why the title says chrome extension? Its also for Firefox! I didn’t even first notice that this post was relevant to me also!

              1. 3

                I had the same reaction initially, as I use Firefox too. However, Firefox support was only added 11 hours ago, so the title was correct at submission time. :)

                1. 3

                  When this was posted, only Chrome was supported. I’ve edited the title to reflect that it supports more than just Chrome now.

                  1. 1