You are trying to smuggle two branches that have no common ancestor. Git can do this, but does not allow it until you are sure that you know exactly what you are doing.
If you are sure that you need to merge these branches, do this:
git merge --allow-unrelated-histories patch-1 CLang
Just in case: I suspect that branches appeared due to an error in the workflow: the branch for development was confused with the branch for documentation. I'll tell you a little more.
GitHub allows you to create websites (called GitHub Pages), accompanying a certain project (repository) or representing a personal user page. One of the options for storing the contents of such a site is in the general repository of the project, but in an "orphaned" branch under the name gh-pages .
Probably someone tried to set up GitHub Pages and created such a thread. The first commit of this thread contains the template for the site page. On the graph, this is the first (left) commit of the red line. After the master branch of the same repository was rearranged to this branch and development continued in it. According to the graph given in the question, it can be seen that on the fifth kommite the branch CLang departed from it.