Comment

Comment by quectophoton

GitHub's greatest win has been convincing everyone that "pull request" means having a web interface for code review as well (conflating sharing code with reviewing it) and can only be done by creating accounts in websites; and that patch-based workflows can only be done through email.

They even convinced people that repository clones are called "forks" when they have a web interface but not when they're local.

I like that this project is trying to remove those misconceptions.

Of course if the contributor already has their own publicly available repository, then they can send you a pull request through HackerNews if they want.

    Hey I made some performance improvements, they are at https://example.com/git-pr.git on branch `improvements`.
That was a pull request. You can check out changes with `git pull https://example.com/git-pr.git improvements` and review them.

I've also done ad-hoc patches through Slack, using `git diff` and `git apply` but the idea is the same.

And yes I've also done stuff like this but with just `git push` instead of `git format-patch | ssh` (you want to look at pre-receive hook) messing around with friends on IRC. The problem is not how possible or easy it is, the problem is "just" gaining traction and having a good plan for moderating The Stuff People On Internet Will Upload.

See GitTorrent for another (unrelated) example of a good idea that never gained traction.

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton