@RL_Dane what about #SourceHut? How does it compare to github?
@mahmoudajawad @RL_Dane I love sourcehut but one might need a while to get used to it coming from Github or similar services. There are no Pull/Merge Requests but patches. There is an issue tracker and build tools and so on, but they are more separated and flexible.
I think a big problem (and I'm saying this as a total novice to the source code revision management game) is that #GitHub != #Git, and that is causing some real confusion.
Once again, #Microsoft has managed to #EmbraceAndExtend and break both compatibility, and the mental concept of what git actually is. And they didn't even create GitHub, although I wonder if it was more of a vanilla Git service before they bought it out.
@RL_Dane @mahmoudajawad GitHub was already the way it is when MS bought it. I'm not sure if Pull Requests are GitHubs invention but they where for sure the biggest source of adoption.
It's honestly all a bit over my head, but does this page lead you to believe that pull requests aren't exclusive to #GitHub?
https://docs.codeberg.org/collaborating/pull-requests-and-git-flow/
cc: @Codeberg
@RL_Dane @mahmoudajawad @Codeberg Pull Requests are definitely not exclusive to GitHub. They can be found in many suites like Gitlab, Gitea, Codeberg and others. They sometimes have different names. I think Gitlab is calling them Merge Requests for example.