to fully cover the possibilities for GitHub pages sources, as per the docs, I guess we'd need this to.
(this is an extension of #3)
I'm a little cautious about this one, because deploying to docs/ you might:
overwrite something unintentionally using this action
pollute the commit history (I guess this is part of the docs/ logic)
bloat your repo size (see below)
We'd need to be quite careful with the git command as well; currently we can just write to some branch and delete all of its history and be done with it.
So this seems to add a lot of complexity.
Also, I just think docs/, if used at all, should be used by directly committing to it, not through some CI/CD.
to fully cover the possibilities for GitHub pages sources, as per the docs, I guess we'd need this to.
(this is an extension of #3)
I'm a little cautious about this one, because deploying to
docs/you might:docs/logic)We'd need to be quite careful with the git command as well; currently we can just write to some branch and delete all of its history and be done with it.
So this seems to add a lot of complexity.
Also, I just think
docs/, if used at all, should be used by directly committing to it, not through some CI/CD.