Not familiar enough with this particular project to know, but a quick glance at the commit log shows some overlap in commit authors, so I guess there is at least some level of sharing happening, probably just not through merges.
But being familiar with this kind of project in general, the branches will probably never be fully merged even in the future, just doesn't make much sense because they are server software targeting very different versions of a game client. There are also two other branches, but they "only" diverged by like one or two thousand commits so far.
When your branch becomes a fork
Is that even a joke or a fact statement at this point?
Not familiar enough with this particular project to know, but a quick glance at the commit log shows some overlap in commit authors, so I guess there is at least some level of sharing happening, probably just not through merges.
But being familiar with this kind of project in general, the branches will probably never be fully merged even in the future, just doesn't make much sense because they are server software targeting very different versions of a game client. There are also two other branches, but they "only" diverged by like one or two thousand commits so far.
Average pull request
What is a "merge"?
Oh baby rebase me Rebase me No mohr.
I have no idea how your brain did the gymnastics to get to that, but I'm a fan nonetheless.
What is noun?
Oh baby (don't) verb me
(Don't) verb me
No mohr.
Well, at least they committed to it!
At what point have you just forked yourself in the same repo?
Edit: actually that's basically what it is
I wonder how many merge conflicts there will be.
master? tut, tut, tut