Repository navigation
ci: replace unverified third-party GitHub Actions with first-party steps - #271
Draft
ffumero2003 wants to merge 1 commit into
Draft
ffumero2003 wants to merge 1 commit into
ffumero2003 wants to merge 1 commit into
Conversation
Use GitHub CLI and inline run steps for releases, Pages health checks, and gh-pages publishing. Retain the original action blocks as commented fallbacks and keep build and Maven publish commands unchanged.
Contributor
Author
|
Converting to draft and parking this. On hold pending internal coordination on this repo's ownership; the branch and work are preserved to revisit later. Not for merge in the meantime. |
This branch has not been deployed
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
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.
Context
Part of the organization-wide GitHub Actions governance effort: actions owned by individual developers should not run in our CI/CD. This replaces each such action with a first-party step we control. GitHub-official and verified-vendor actions, and the package publish steps, are unchanged.
Changes
softprops/action-gh-release(deploy.yml) →gh release create(reruns viagh release edit+gh release upload --clobber), preserving tag, title, notes, and flags.crazy-max/ghaction-github-pages(ci_cd.yml) → an inlinegit pushof the built Javadoc to thegh-pagesbranch. The build job gainspermissions: contents: write, required for that push.crazy-max/ghaction-github-status(ci_cd.yml) → a read-only query of the githubstatus.com API for the Pages component, preserving themajor_outagethreshold. (The original action set no commit status, so none is created.)Verification
gh releasecommand routing verified.gh-pages;gh release createand its--clobberrerun succeeded (same release id, assets replaced); and the Maven/GH-Packages publish steps correctly skipped (guarded to the private repository). Cleanup completed; the canonical repository was untouched.master;actionlintintroduces no new diagnostics versusmaster(the remainingSC2035/SC2086notes pre-exist onmaster).master, so they first execute on merge;gh release createruns only at a tagged release. The commented-out originals remain as a fallback until those first runs are green.Closes #270