Add the Publish Site workflow - #334
Merged
Merged
Conversation
Calls the shared workflow added in codehaus-plexus/.github#62, so the site can be published from the Actions tab instead of from a maintainer's laptop. Single-module project, so no multi-module input: the POM binds scm-publish to site-deploy already. Exposes dry-run so the first publish here can be verified without committing to gh-pages. Part of codehaus-plexus/.github#58
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of codehaus-plexus/.github#58. First caller for the shared workflow merged in codehaus-plexus/.github#62 — deliberately one of two before the sweep, so the shape can be reviewed.
This is the single-module form. Three lines of actual configuration:
No
multi-moduleinput — this POM already bindsscm-publishtosite-deploywithcontentset totarget/site, so the default path is correct.After this, publishing the site is Actions → Publish Site → Run workflow rather than a maintainer running Maven locally with the right profile and credentials. That is the whole point: this site was last published in April 2026, and across the org
gh-pagesdates ranged from May 2023 to June 2026 purely because it depended on someone remembering.Please run it with
dry-runticked first. That builds the site and checks outgh-pageswithout committing, so the token permission and thepubScmUrlrewrite can be confirmed before anything goes live. I have not run it — the first real publish should be a maintainer's call, not mine.The multi-module form is in the companion PR on modello; the two together are all the variation there is.