4 ms·
My product for GitLab and GitHub does this. This is an example of browsing diffs one by one: https://gitsense.com/rapid-browsing-1.mp4 https://gitsense.com/ra
by sdesol 10y ago
My product for GitLab and GitHub does this. This is an example of browsing diffs one by one:
https://gitsense.com/rapid-browsing-1.mp4 https://gitsense.com/rapid-browsing-1.mp4
And this is an example of bulk diffs browsing:
https://gitsense.com/rapid-browsing-2.mp4 https://gitsense.com/rapid-browsing-2.mp4
You can find the source for the chrome extension at
http://github.com/gitsense/insight http://github.com/gitsense/insight
And the Git indexing engine at
http://gitsense.com/download http://gitsense.com/download
Edit:
It may not be obvious, but for the second example, I'm clicking the right arrow to quickly iterate through the diffs.
- oneeyedpigeon 10y agoYes, that second video is pretty much exactly what I'm looking for. I've been considering implementing it myself as a general-purpose git tool (i.e. not github etc. dependant) - were there any major gotchas? Do you need to pre-cache commit or diff info. or is it efficient enough to do everything in real-time?
- sdesol 10y agoThe major gotchas is building the indexing engine. Once you have that in place, getting the commit information takes milliseconds. The only time consuming thing is extracting the from and to blobs from the repo. However, that is a one time hit, since you can cache the blobs. For the diff, this is done in realtime with https://github.com/Microsoft/monaco-editor https://github.com/Microsoft/monaco-editor Also my product isn't really dependent on GitLab or GitHub. It works in standalone mode as well.