@faithisleaping@anarres.family
2026-05-05 14:01 UTC
@low@lgbtqia.space Yeah...
MR makes more sense to me because I "grew up" in the mailing list of patches world and what you did at the end of a review was merge your patches. So calling it a "merge request" makes sense.
GitHub, on the other hand, pushed hard on the fork model where everyone has their own fork and they push to that and then submit a pull request to pull their branch into main.
I think at this point the GitHub nomenclature is more accurate with most projects' development flows (including mine) but it still irks me a bit. 😂
Replies (1)
-
@low@lgbtqia.space 2026-05-05 14:09
@faithisleaping@anarres.family I never really understood the naming PR, after all, even with a fork, you are going to merge. So MR makes more sense. (I will probably use PR anyway due to the tools I am working with at work and because it is so ingrained)