Seperate build and deploy of docs

[jimporter]

Seperate build and deploy of docs

[jimporter]

You don't have to push the commit from mike deploy immediately; you can do that later in a separate step. It'll still generate a local commit to your gh-pages branch, but if you don't push the commit, then nothing should change with your hosted docs. I think that should resolve the issue you mention here; unfortunately, there's not an easy way to completely separate the build from the commit in mike; the goal was to use Git branches to manage a lot of the complexity here.

[Wolf2323]

I understand, but i don't know, how i pass a commit to an other job of the same github action build pipeline

[jimporter]

There might be an easier way than this, but at worst, you could just upload the diff of the latest commit as your artifact, and then commit/push it on your deploy job.

[jimporter]

Closing this; I think my comment immediately above is the best solution here, barring some major changes to how mike works. If you need some more pointers on how to get this set up, feel free to comment again though.