After the draft is renamed, the setup action updates the gh-pages branch. This is necessary because changes made by actions cannot trigger other actions (for reasons that I hope are obvious). The gh-pages actions therefore would not run and catch the changes made during setup.
But the rename commit also engages fallback behaviour in the template that allows the gh-pages action to complete successfully and also push to gh-pages.
As both actions are attempting to push to the gh-pages branch, this produces contention that results in one of the actions failing. This is not good, particularly if it means that the setup action is the one that fails.
A fix probably needs to made in the fallback logic in so that the push is not attempted. Maybe the answer is to set PUSH_GHPAGES to false in a copy of the Makefile.
After the draft is renamed, the setup action updates the gh-pages branch. This is necessary because changes made by actions cannot trigger other actions (for reasons that I hope are obvious). The gh-pages actions therefore would not run and catch the changes made during setup.
But the rename commit also engages fallback behaviour in the template that allows the gh-pages action to complete successfully and also push to gh-pages.
As both actions are attempting to push to the gh-pages branch, this produces contention that results in one of the actions failing. This is not good, particularly if it means that the setup action is the one that fails.
A fix probably needs to made in the fallback logic in so that the push is not attempted. Maybe the answer is to set
PUSH_GHPAGESto false in a copy of the Makefile.