The pull-request box looks like a live-demo, so I dug up a URL only to find out it's not :/
A bit of a nit-pick, but if there's only 1 field, I don't need to be told it's required - the '* required' on the singular email field seems redundant. (I understand it's probably the framework you're using, but it just seems weird.)
You only screen shot doesn't show: does your side-by-side diffs support coloring? eg. https://confluence.atlassian.com/download/attachments/298976...
Feature requests:
* A signoff list of people who've reviewed the pull request and feel its ready to accept. This'd be helpful as most of our work is independent / 'remote' (we're not all in the same room together).
* Works on most platforms, or is web based. Each student has their own personal setup that we need to accomodate.
* The ability for a Pull Request submitter to link to other resources, such as documentation, Trello cards, various Github features (code files and issues come to mind)... Basically, it'd be nice for the submitter to provide a short description of how their changes affect the software at a high level. I find most of this exists in our other documentation. Currently we just add a description with the links to the PR description on Github, but maybe you can improve on that.
What "desktop" is your target? Someone recently asked me if I knew a good side-by-side diff tool that worked with GitHub and wasn't written a decade ago. I only knew of a buggy plugin. This, superficially, seems to be what he was looking for. If your target is Apple, he'd likely be thrilled. If it's Linux, I'd be interested.
Is there anything from the content that you dont understand, that I could make clearer?
Is this something that you would use?
The side-by-side diff feature is buried at the bottom, and the whole page seems to imply that there are other features within somewhere, but I can't figure out what they would be (I would love to see screenshots of them!).
I want to know more about "better navigation" and context.
I would love, love, love to talk with you about this. justin@abrah.ms Seriously.
For the other readers.
First up. I find inline diff's really hard to comprehend once they get past a few lines changed here and there. This might be just me, but anecdotally I've found other devs to also feel this.
The better context and navigation is all about seeing the change in the context of the code-base. Small code changes can have large effects. Indifference will allow you to navigate the whole code base rather than just the single change set +/- a few lines. In this way you can get a better handle on what has changed and how it will effect the rest of the codebase.
At this point I want to validate the idea. If you're interested in this please leave your email address. or a comment below. Any feedback would be great!
In the future working for something like bitbucket or arbitrary git repos I think would be a feature that could be added.
