Gitlab/Github should add a feature that any submitted merge requests automatically emails the last author of the code lines being modified, to let them know about the MR and provide any feedback if needed.
Or maybe someone has wrote a bot/Git hook for that?
For a linux user, you can already build such a system yourself quite trivially with git blame directly, piping it through grep awk and git log to email yourself that list with a cron job.
Long time ago, HTTrack came very handy for me at work. We created a PHP/Mysql application to store data for a census of industrial sites and related info. Some day my boss tell me the customer wants this census being delivered to them in a auto-startup CD-ROM which was very fashionable at that time, I used HTTrack to download every page of our PHP database and all be browseable offline from the CD-ROM, the auto-startup just launch the browser at the index page.
Oh, this brings back memories of my first steps with Gentoo linux, when I failed at setting up the display (XFree86 back then) or configure it properly, I remember browsing Gentoo wiki pages with Lynx to bring it back.
I'm on Linux and I just use one keystroke to switch (F2). I have F1 F2 F3 F4 keys binded to change to virtual desktops 1 2 3 4. 1 -> Console(s) 2 -> Editor (sublime) 3 -> Browser (Firefox) 4 -> Misc (File browser, other apps)
Another happy customer of Sublime Text here, but still not dare to take the step to buy SublimeMerge, I'm pretty well served in console for my git use, except for 'git blame' that I prefer to do in a UI tool, but SublimeMerge blame support is awful.
Because c++ codebases nowadays are full of commits that just reformat or refactors code (clang-format, update to smart pointers, update to new api, etc) and so if I just want to find out the original commit which introduced that codeline (because I want to know the _original_ motivation for it), it means in Gitlab I just need to click 3 or 4 times on said button to skip all such formats/refactor commits until I get to the one I'm interested in. That is easy in Gitlab, while SublimeMerge just let me click on the SHA of the last change for the codeline, and from there I'm lost I don't know how to keep "blaming back" like Gitlab easily let me.
- In the same vein of easy skipping blame changes until the one you want, it would help a lot supporting the git config setting blame.ignoreRevsFile:
https://wezterm.org/