ci: pin docs-engine to v0.3.0 for the default Contributing page - #15
Merged
Merged
Conversation
The shared jlt-commons/ci-builds site workflow still defaults its docs-engine-ref input to v0.2.0. v0.3.0 adds an automatic Contributing page to every generated project guide, purely additive and overridable by a project's own docs/guide/contributing.md. Pin this project to v0.3.0 explicitly so the new page reaches the live site now, and so the build stays reproducible the next time the shared workflow's own default moves on.
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.
docs-engine v0.3.0 adds an automatic Contributing page to every project's
generated docs site. It's purely additive, needs no config, and any
project can still override it with its own docs/guide/contributing.md.
The shared reusable workflow, jlt-commons/ci-builds/.github/workflows/site.yml@main,
takes an optional docs-engine-ref input that still defaults to the old
v0.2.0. Pinning this project to v0.3.0 explicitly is what actually gets
the new page onto raylib-jlt's live site, and it keeps the build
reproducible even after the shared workflow's own default moves again.
Same change, already landed for raylib-android as the reference pattern: