Repository navigation
DOCOPS-213 Use the reusable trigger and update the generate workflows - #91
Merged
Merged
Conversation
Add docs-trigger-builds.yml (a call to reusable-docs-trigger-builds.yml in docs-tools), update docs-generate-html.yml to take publish-env from the trigger instead of hardcoding the dev and prod branch, and add docs-generate-pdf.yml. All three are the docs-template versions.
Collaborator
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
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.
Part of DOCOPS-213 (https://linear.app/neo4j/issue/DOCOPS-213/roll-out-the-reusable-trigger-and-generate-workflows-to-the-docs-repos).
Moves the repository to the docs-template build workflows:
docs-trigger-builds.yml(new): callsreusable-docs-trigger-builds.yml@v2, which reads the dev and prod branch from the branch record in docs-publish and the playbooks, and triggers the builds the pushed branch belongs to.docs-generate-html.yml: takespublish-envfrom the trigger. The hardcodedDEV_BRANCHandPROD_BRANCHand theprepare-ref-envjob are gone.docs-generate-pdf.yml(new): builds a PDF. The reusable triggers it for the dev branch only.Dev and prod are both
mainin the branch record, so a push tomainbuilds and publishes to both environments, plus a PDF todev.npm run verify:previewpasses with no warnings or errors in the log.