Install stable templates if using stable build #518
Merged
Conversation
This file contains 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
Signed-off-by: itowlson <ivan.towlson@fermyon.com>
itowlson
force-pushed
the
stable-build-needs-templates-from-tag
branch
from
b2a4e48
to
8bb093d
Compare
|
Perhaps we should have a |
|
chuckle agree that Shall I merge this now so we can push new docs, and then get it to use the default tag when we've decided what to call it? |
|
cc @vdice for updating the stable docs website. |
radu-matei
approved these changes
May 25, 2022
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.
This is a partial fix for #517.
It's partial because we need a longer term strategy for things like this, whether that's keeping
HEADon the 'stable' branch or auto inferring the matching tag or what. Perhaps a topic for the Spin meeting. It's also partial because it's not sustainable, we don't want to have to rev this as part of every release!Is it possible to get this fix rolled out to the 0.2.0 docs site, please?