When you push to multiple branches in rapid succession (as happens when I am doing docs copyediting on unity/v5.0, unity/v5.1, core/v7.0, and core/v7.1 in a single session), the Auto Publish Branch action tries to run for all branches at once, leading to a timing conflict on the gh-pages repository.
I tried adding a concurrency group to the workflow, but that just means that instead of "one wins, three fail", it does "one wins, a second gets queued, and two get canceled".
There must be a better way, but it was not immediately obvious.
This is very low priority; for my workflow, I can avoid it by just waiting a minute or two between different branches' pushes.
When you push to multiple branches in rapid succession (as happens when I am doing docs copyediting on unity/v5.0, unity/v5.1, core/v7.0, and core/v7.1 in a single session), the Auto Publish Branch action tries to run for all branches at once, leading to a timing conflict on the
gh-pagesrepository.I tried adding a concurrency group to the workflow, but that just means that instead of "one wins, three fail", it does "one wins, a second gets queued, and two get canceled".
There must be a better way, but it was not immediately obvious.
This is very low priority; for my workflow, I can avoid it by just waiting a minute or two between different branches' pushes.