Thank you, though pretty close, our approaches are slightly different. My main focus is use case, I did not implement the social features of a repository, because those are things that happen happily in a browser.
But project/merge requests/gists are things that have a lot of sense to happen in the commandline /instead/ of within the browser. So basically, his solution is more feature complete on the social side, whereas I implemented more the repository interaction side (like creating gists, or fetching a PR).
So for sure he's got a point for portability being a bash script, but still python3 is begining to be widespread enough.
I mean, if debian-stable got it, you can consider it's everywhere…
But project/merge requests/gists are things that have a lot of sense to happen in the commandline /instead/ of within the browser. So basically, his solution is more feature complete on the social side, whereas I implemented more the repository interaction side (like creating gists, or fetching a PR).
So for sure he's got a point for portability being a bash script, but still python3 is begining to be widespread enough.
I mean, if debian-stable got it, you can consider it's everywhere…