33 ms·
I prefer Gitlab's "merge request" to Github's "pull request", too bad Kalithea chose "pull request" (super minor thing that does not really matter though).
by apples_oranges 6y ago
I prefer Gitlab's "merge request" to Github's "pull request", too bad Kalithea chose "pull request" (super minor thing that does not really matter though).
- k__ 6y agoWhat's the difference?
- webmaven 6y agoThe point being made is that 'merge request' is a better description than 'pull request' for the same functionality, where one requests that a repo pull from your fork's branch and merge it's commits.
- ptx 6y ago> one requests that a repo pull from your fork's branch So why isn't "pull request" a good name for a request to pull from a different repo?
- moonchild 6y agoThe mechanism is a pull, followed by a merge. But what's interesting about the transaction is that your tree is merged with the upstream tree; the pull is just an implementation detail. You would be just as happy if the merge happened somehow that didn't involve a pull, but you wouldn't be very happy if there were a pull but no merge.
- steviedotboston 6y agoyeah, "pull request" is terrible terminology. It confused me for years.