junit5
junit5 copied to clipboard
Use actions/deploy-pages for deployment to GitHub Pages
Currently, JUnit documentation publishes to a gh-pages branch which creates wasteful commits in git history, it consumes space for those who clone the repository.
It would be great to drop gh-pages branch altogether.
What do you think of using actions/deploy-pages instead so the contents deploy to Pages without being comitted to git?
See:
- https://github.com/actions/deploy-pages
- https://gohugo.io/host-and-deploy/host-on-github-pages/#step-7
Currently, JUnit documentation publishes to a
gh-pagesbranch which creates wasteful commits in git history, it consumes space for those who clone the repository.It would be great to drop gh-pages branch altogether.
I wholeheartedly agree. 👍
What do you think of using
actions/deploy-pagesinstead so the contents deploy to Pages without being comitted to git?
I wasn't aware of this alternative deployment mechanism. Thanks for bringing it to our attention!
IIUC using actions/deploy-pages requires uploading an artifact that contains all resources via actions/upload-pages-artifact in a previous step. Since we deploy only the docs for one version but would like to keep the docs for older versions available, how would that work?
Looks like partial deployments are not planned: https://github.com/actions/deploy-pages/issues/73#issuecomment-1477234353
The way out is to build the full site and publish it as a single unit.
So we'd have to store it in some place (let's say a Git repo), add the new content, and publish it from there. Sounds a lot like the existing approach… 🙃
An alternative would be to deploy the junit5 subdirectory as part of https://github.com/junit-team/junit-team.github.io
If you would like us to be able to process this issue, please provide the requested information. If the information is not provided within the next 3 weeks, we will be unable to proceed and this issue will be closed.
Superseded by:
- #4663
- #4664