Refactor github workflows to add CI checks#226
Draft
vicenteqa wants to merge 1 commit into
Draft
Conversation
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.
Description
This refactors the docs GitHub Actions workflows to provide safer and more consistent PR validation.
The motivation for this change is that merging Dependabot PRs in this repository was not safe enough: several dependency and GitHub Actions updates had little or no meaningful PR validation before being merged.
Changes included:
Docs CIworkflow for pull requests affecting workflows, tool versions, docs content, the Antora site, or the UI bundle.main.npm ci,npm run format:check, extension tests, UI bundle build, and Antora site generation as part of PR build validation.Fixes: N/A
How was this tested?
Documentation changes
Yes
Updated
content/trento-docs-site/ci-and-publishing-overview.adocto describe the new PR CI workflow, reusable workflows, publishing behavior, SUSE docs validation behavior, and extension test coverage.Additional information
The PR CI workflow does not publish or deploy anything. GitHub Pages deployment remains limited to the publish workflow triggers: push to
main, scheduled runs, and manual runs.