51–60 of 75 posts
Earlier quoted context omitted.
I have to agree. The fact that you still cannot do side by side diffs on pull requests makes it a less than useful code review tool.
What's the difference between a diff and a side-by-side view of two files? I'd (usually) prefer the former.
Hmm, neat. I've added all the bike sharing networks I can think of to a repo[1], and for all you NY bike sharing lovers, there you go[2]. I don't think I will update it to work in 'real time' because it would not make much sense, but it was fun to play with. [1]: https://github.com/eskerda/cb-geojson/blob/master/networks.g... [2]: https://github.com/eskerda/cb-geojson/blob/master/citibikeny...
Earlier quoted context omitted.
I second the call for supporting books. There are already quite a few books being published on GitHub and it seems like an almost natural way to collaboratively write a book that could forever kept up to date. Not sure if anything has been done specifically to support writing a book on GitHub.
I'm a grad student who writes lots of papers in LaTeX with collaborators. We use git most of the time, but git works most painlessly when you tweak it to ignore whitespace and to use word diffs. For example, let's say that my collaborator says "oh, I pushed a new diff" and now I'm curious what he added. Running: git pull && git log -p -w --color-words lets me see exactly which words he added/removed/changed ignoring…
Hmm, neat. I've added all the bike sharing networks I can think of to a repo[1], and for all you NY bike sharing lovers, there you go[2]. I don't think I will update it to work in 'real time' because it would not make much sense, but it was fun to play with. [1]: https://github.com/eskerda/cb-geojson/blob/master/networks.g... [2]: https://github.com/eskerda/cb-geojson/blob/master/citibikeny...
EDIT: nevermind https://github.com/bikesharebot/bikesharestats/blob/master/c...
Earlier quoted context omitted.
I have to agree. The fact that you still cannot do side by side diffs on pull requests makes it a less than useful code review tool.
What's the difference between a diff and a side-by-side view of two files? I'd (usually) prefer the former.
https://bitbucket.org/birkenfeld/sphinx/pull-request/146/res...
Click 'Side-by-Side Diff'. Github has a lot going for it, but bitbucket is the clear UX win as far as reviewing pull requests goes.
Earlier quoted context omitted.
What's the difference between a diff and a side-by-side view of two files? I'd (usually) prefer the former.
It is difficult to follow the code that's been added when all the deletions/diffs get in the way.
http://screenshots.gitsense.com/index.html
that illustrates where side by side becomes a requirement for me. Yeah I can make sense of things with a unified view but the side by side really makes things more obvious.
Note you can find this diff at github at https://github.com/joyent/node/pull/5615/files#L0L80
I'm increasingly thinking that the biggest competitor we have isn't other forum software (who aren't innovating), but Github. Our startup ( http://microco.sm/ ) is working on improving communities, which most people read as vBulletin, phpBB, Discourse... but my view is simply that if you have a group of people together around some interest (topic, locality, project) that they want to communicate, share, transact at e…
I'm increasingly thinking that the biggest competitor we have isn't other forum software (who aren't innovating), but Github. Our startup ( http://microco.sm/ ) is working on improving communities, which most people read as vBulletin, phpBB, Discourse... but my view is simply that if you have a group of people together around some interest (topic, locality, project) that they want to communicate, share, transact at e…
Whilst I have no insider knowledge, I highly doubt GitHub has any desire to expand outside of the development community.
Earlier quoted context omitted.
EDIT: nevermind https://github.com/bikesharebot/bikesharestats/blob/master/c...
That's fucking sick. Nice work man.
One could question, who would want maps on github? Sometimes one cannot know what something can be used to until being able to actually use it, that should be the whole point on technology.
Earlier quoted context omitted.
It is difficult to follow the code that's been added when all the deletions/diffs get in the way.
I agree. I find that unified diffs work well 90% of the time but when it doesn't it can be crippling. I've attached some screenshots at http://screenshots.gitsense.com/index.html that illustrates where side by side becomes a requirement for me. Yeah I can make sense of things with a unified view but the side by side really makes things more obvious. Note you can find this diff at github at https://github.com/joyent/n…