mike-cardwell 3 months ago

I wonder how many devs out there are going to basically hand over access to their companies property (private code repos) to this random guy by "signing in with github", without even thinking about what they're doing.

  • hobofan 3 months ago

    By default access to private organization repositories is not given, and has to be specifically requested from the organization.

  • typpo 3 months ago

    I'm a bit sad to see this cynicism at the top of a Show HN thread. This project is a fun way to browse code history and it's done with an interesting visual style. It's also open source.

    I would think someone trying to view a private file is aware that they are signing in via Github to share it. Github Oauth also explicitly states that code access is shared. So, I don't think it detracts from pomber's project.

    • mike-cardwell 2 months ago

      There was nothing cynical about my comment. So you are sad for no reason.

      The privacy implication of handing over access to private code repos to a complete stranger is real, and this project should warn users that this is what they are doing, front and center.

      This project could (and arguably should) have been built in such a way that it didn't require you to hand over read access to your private code repos. It could have been built as a browser addon or greasemonkey plugin.

      "I would think someone trying to view a private file is aware that they are signing in via Github to share it." - I don't agree. That is why I wrote my comment. I think lots of people would not even consider the implications of what they are doing.

      This project doesn't even appear to have a privacy policy or terms and conditions, of any description, so who knows what they're doing with your source code. They could legitimately clone all the private repos that you give them access to, and keep them for statistical analysis or for personal commercial exploitation. Maybe you created a private repo for a NodeJS project but didn't switch the default license specified by NPM from ISC because nobody else should ever have seen the code. Now you've just given your code to a third party with a license that is functionally equivalent to MIT. They can chuck it up in a public github repo and let whoever wants to, use it.

    • kevintb 3 months ago

      Agreed, but this is the default attitudes of most HN comments - to criticize or nitpick something small.

      • olafure 2 months ago

        Giving someone else access to your organisation's private repo is not a small thing in my opinion.

      • nohnce 2 months ago

        I think we can do our part to vote up the comments that are more supportive and change the norm.

  • alanbernstein 3 months ago

    Where is the "sign in with github" prompt?

    • TheArcane 3 months ago

      Comes up if you request githistory for a file in a private repository

mike-cardwell 3 months ago

Seems the project is MIT licensed and written in JavaScript so presumably somebody could package it up in a browser extension so there are no privacy issues when viewing private repos: https://github.com/pomber/git-history - He does have browser extensions but they just look like they redirect you to the service.

btbuildem 3 months ago

The slick movement makes it hard to see what the changes were -- a classic diff would be orders of magnitude more effective here.

  • dkoston 3 months ago

    Came here to say the same thing. Having to click back and forth in history to see the changes is time consuming. Function over flash please

  • imhoguy 3 months ago

    Wide multi-pane diff with committer over each pane and horizontal scroll to navigate.

koboll 3 months ago

This is very cool.

One suggestion: The long horizontal sliding animation seriously detracts from the user experience. It makes it difficult to track what changed because areas of the code go briefly blank while the next bit of code is sliding in.

Would be a lot less difficult to track changes if new lines of code simply faded in in-place and pushed code around them up and down.

cpayne624 3 months ago

This is super-slick. Suggestion, scroll to the (top) changed line before the change animation to reveal changes in large files that happened out of viewport. Nice work

beefman 3 months ago

I was always flabbergasted github doesn't provide this.

Also basic info that every other file browser in the universe shows, like file size.

  • pizza 3 months ago

    Been wanting file size info in the file explorer in github for years now, it would make it so much easier to find out where to look first when exploring repos for the first time.

saagarjha 3 months ago

If only GitHub could do this themselves instead of falling over if you try to run blame on any reasonably large repository…wait, hold on, it looks like this website does as well. Aww…

  • oneeyedpigeon 3 months ago

    Exactly. I have wanted this on github for so long — even the animation is beyond what I'd like, I'd settle just for a 'prev/next' button that takes you from change to change. I'm pretty close to just coding it myself for local use.

    • graphpapa 2 months ago

      Vim fugitive makes this pretty straightforward `:0Glog`. I imagine many other git wrappers provide similar functionality

andrew_ 3 months ago

YMMV - I'd like to see highlighting of what's changed, as it's difficult to track multiple changes with the animations. The old stand-by red and green for diffs could work, with the old content eventually fading out or some such - probably a more elegant want to achieve that but hopefully you get the gist.

  • Zitrax 3 months ago

    Exactly, I don't see this as very useful right now, looks more like fancy animations.

    To actually see what happened I found myself triggering the same animations again and again.

chatmasta 3 months ago

For a similar visualization, but at the repository level, check out Gource [0]

[0] https://github.com/acaudwell/Gource

  • cpr 3 months ago

    This is a helluva fun thing to run on a nearly 30-year-old repo (in our case, started with RCS, eventually ending up in git).

    Takes you right down memory lane and really gives you a feel for how your codebase has evolved, and the place of each contributor.

jmiserez 3 months ago

Been looking for something like this for ages. Is there a version that works with local repos?

EDIT: at least for emacs, there's https://gitlab.com/pidu/git-timemachine

EDIT2: and a different one for Atom with a nice plot: https://github.com/littlebee/git-time-machine

  • pomber 3 months ago

    Not yet, but I want to add a CLI for local repos soon

    • lixtra 3 months ago

      Within 30 minutes two people want to give you money to run it on private servers. The entrepreneurial answer to that is: Write to sales at githistory.xyz, we’ll figure something out.

    • thegabez 3 months ago

      Please do, would love this!

linkmotif 3 months ago

Not to be that guy but: git log -p $file. Works great IMO.

  • u801e 3 months ago

    That will show you the diffs, but if you want to see the files side by side, you could do something like:

      diff -y <(first_sha1:path/to/file) <(second_sha1:path/to/file)
    • u801e 3 months ago

      The command should actually read:

        diff -y <(git show first_sha1:path/to/file) <(git show second_sha1:path/to/file)
  • pault 3 months ago

    Just the other day I had a coworker freak out when he saw me do this. It baffles me how a professional developer could use git for years and never read the manual.

    • linkmotif 3 months ago

      yep. Or even just some blog posts or whatever. Git is the worst-presented tool I think, it’s a shame.

rectang 3 months ago

Feature request: Any chance for `--follow` to track the history of files that have moved?

ignaloidas 3 months ago

This still needs performance improvements - on bigger files with longer history the transitions between commits get choppy, it shows only the newest 10 or so commits and doesn't load older ones, e.g. [0] has around 2500 lines and a history of around 200 commits. Usability is horrible for such files.

[0] https://githistory.xyz/godotengine/godot/blob/master/servers...

buremba 3 months ago

Could you please make a bookmarklet as an alternative to Chrome extension?

  • pedroborges 3 months ago

    I just built a simple bookmarklet for myself. I hope you like it!

    javascript:(function(l){l.host.match('github.com') && (l.href = l.origin.replace('.com', '') + '.githistory.xyz' + l.pathname)})(window.location);

  • mhw 3 months ago

    Not quite as pretty, but here's a bookmarklet that allows you to go back by one commit in the github.com blame view (e.g. https://github.com/babel/babel/blame/master/packages/babel-c...). It basically finds the most recent 'View blame prior to this commit' link and follows it.

    javascript:(function(l){l.host.match('github.com') && (l.href = Array.prototype.slice.apply(document.querySelectorAll('.blame-hunk')).map((d) => [new Date(d.querySelector(".blame-commit-date time-ago").getAttribute('datetime')), d.querySelector(".blob-reblame a") && d.querySelector(".blob-reblame a").getAttribute('href')]).sort((a,b) => a[0] < b[0])[0][1])})(window.location);

lez 3 months ago

It would be even more awesome than it is, if:

* A "blame" column could be turned on at the left, showing output from "git blame". * When hovering over a line in the blame column, the main window shows the historical version of the file when the commit was born. Commit message appears on the left (even more left). * When it is clicked, the timeline jumps there.

I understand it would be a lot of work, but it would be a super valuable tool for browsing file history in git.

edwinyzh 2 months ago

Granted github access, but always get "GitHub API rate limit exceeded for your IP (60 requests per hour)". This is a free github account, is it normal? Using Chrome Version 72.0.3626.96 (Official Build) (64-bit)

dkarp 3 months ago

What are people's opinions of this type of diff? Are there certain cases where it's more useful to see it like this than the usual green/red above and below style?

Would be great if there were studies on this. What is the easiest to interpret: in-line, above/below, side-by-side, other options I don't know exist

  • xori 3 months ago

    It's not really a diff, it's a snapshot.

    If we had the past on the left, and the future on the right, then I'd call it a diff.

    • dkarp 3 months ago

      You're right, it's snapshots with the diff animated between them.

      A lot of people complaining here about it being difficult to see the diff haven't understood what this is for then. But then, what is it for? Just to look pretty?

      Is it to easily find the state of a file at a particular date or commit? But then it'd be hard to do if there were a lot of commits. Would be nice to know what use case the creator had.

aboutruby 3 months ago

I think keeping some color coding for the lines that got added / removed (better for the characters added / removed) would be nice (e.g. just an almost transparent background color on the lines / characters like Github does).

Otherwise great idea and I really like the URL-based projects.

mark_l_watson 3 months ago

Thanks! That is very cool. Definitely will add that to my workflow.

nullandvoid 3 months ago

This looks amazing thanks! Is there any chance of a vs code port happening? Turns out I thought my current solution was nice but is actually a janky experience compared to this

jakemor 3 months ago

This is really cool.

The animations are great – but I think you should speed em up a bit. The long ease-out period makes it tough to concentrate on small changes. Will most definitely use this!

nikofeyn 3 months ago

coming to github from perforce due to a job change, i have never gotten back to the point i was at with perforce in terms of expertise, flexibility, and custom scripting. some of it is because of size of team changes, but most of it is github missing features and git being, in my opinion, overly complicated. for example, perforce has a very nice file tracking ui that helps navigate changes, braches, renames, etc.

miki725 3 months ago

This is amazing! Simple and elegant. This puts any other history viewer to shame. Now I wish this was available for GitHub enterprise for work code.

egze 3 months ago

This is nice. Can it be done with a browser extension only, without a web service? (to make it work for private repos)

garfieldnate 2 months ago

I like this a lot, but every line of text is cut in half in the display for me (Chrome 71).

royalghost 3 months ago

This is great. Would be even cool if changes are shown at code level and not line.

sidcool 3 months ago

Pretty neat. Have seen this submitted before I think. But good visualization.

elamje 3 months ago

I don't know if I'll use this much, but that is super cool. Props!

  • noufalibrahim 3 months ago

    My thoughts exactly. It's nice to see and probably very satisfying for the creator. I can also imagine using this in some circumstances especially during presentations or teaching.

    For my daily work, one obvious problem is that I can't see exactly what changed between revision n and n+1. That's what really makes diffs + commit messages useful. With the slick animation, I know where it changed but the information on what exactly was modified is lost and with it, most of the reasons why I use git diff at all.

masha_sb 3 months ago

maybe have a sidebar, with vertical timeline - dates and profile?

confounded 3 months ago

Wish there was something like this for magit!

jibolso 3 months ago

Very neat implementation.

Davidbrcz 3 months ago

git-timemachine does it for emacs for those who don't know.

  • rcfox 3 months ago

    I like vc-annotate. (Bound to `C-x v g` out of the box for me.)

    Besides showing blame-type information for each like, you can also press 'p' and 'n' to go to previous or next commits; you can press 'l' to view the commit message for the last commit on the line you're at; you can press 'd' to show the diff for the line you're at.

  • dtornabene 3 months ago

    thanks! I had no idea this existed, and its awesome

dtornabene 3 months ago

this is very cool, nicely done

sergiotapia 3 months ago

Nifty, but shouldn't this be an open source app? Who would give you access to their repos?