Update docs script and ref/stdlib.html #1153
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
Various things that make it easier for me personally to use: - Use an HTTPS pull URL (still the SSH push URL). This is because pulling over HTTPS doesn't need authentication but pushing needs me to tap my security key; cloning over HTTPS halves the number of taps I need. - Don't require libjsonnet.wasm to exist - we can just keep the existing one from the gh-pages branch if there isn't a newly built one to use. - Require running on a TTY and prompt the user for confirmation before the push. Probably not what we want long term but I was running the script a lot to check things and didn't want to actually push then.
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.
Various things that make it easier for me personally to use:
Use an HTTPS pull URL (still the SSH push URL). This is because pulling over HTTPS doesn't need authentication but pushing needs me to tap my security key; cloning over HTTPS halves the number of taps I need.
Don't require libjsonnet.wasm to exist - we can just keep the existing one from the gh-pages branch if there isn't a newly built one to use.
Require running on a TTY and prompt the user for confirmation before the push. Probably not what we want long term but I was running the script a lot to check things and didn't want to actually push then.
Then update docs/ref/stdlib.html by running update_web_content.sh. We might want to get rid of that file; if not then we'll probably need to add an automated check that it's not out of sync with the source stdlib-content.jsonnet.