The default publishing source for a project site is the gh-pages branch. If the repository for your project site has a gh-pages branch, your site will publish automatically from that branch.
This PR needs to be closed, the branch renamed, and resubmitted. And the associated pipeline should trigger on master, and then write to gh-pages ((that's just what mkdocs gh-deploy does)) -- it shouldn't be watching gh-pages itself.
This branch cannot be
gh-pages
. As you probably knowhttps://help.github.com/en/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites
This PR needs to be closed, the branch renamed, and resubmitted. And the associated pipeline should trigger on
master
, and then write togh-pages
((that's just whatmkdocs gh-deploy
does)) -- it shouldn't be watchinggh-pages
itself.