Can we support deploying from tags? about deploy-pages HOT 7 CLOSED

I don't have an ETA yet because we are still planning for it but just a heads up that we are prioritizing this work.

from deploy-pages.

👋 That's more of an Actions problem. What is missing is the concept of protected tags on environments.

We cannot allow Pages deployments on non-protected environments (this is our security paradigm for Actions based deployments).

No ETA yet but we will be adding support for that.

A workaround for now could be to have two workflows:

• A first one that runs on tag creation like you have, run a build and push content to a branch
• A second one that does the deployment from the branch

from deploy-pages.

I have a similar workflow; this would be a very useful feature.

Regarding the suggested workaround, doesn't this have all the disadvantages of the old gh-pages method (filling a branch with generated content, blowing up the size of the repo, etc)?

from deploy-pages.

That's why it's called a workaround 😅

from deploy-pages.

@yoannchaudet is it enough to break this into two workflows?

E.g. I use upload-pages-artifact with a workflow that runs on on.push.tags and then start/trigger another workflow once that completes?

I was thinking, or on.workflow_dispatch or something like a on.workflow_run (with types: ["completed"] filter).

from deploy-pages.

We made changes to the security validation a while back. You should be able to deploy from tags now. With the caveat that you have to drop the environment protection rules. Check #151 (comment).

from deploy-pages.

@yoannchaudet Amaze! It worked. 🎉

For whoever else needs it, I ended up with a variation of this starter workflow as I had to trigger jekyll as well now.

TL;DR — do my release in one job and then start another with the correct token permissions to update the page.

from deploy-pages.