k6 Studio documentation #1778
Merged
k6 Studio documentation #1778
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
* Split publishing workflows Signed-off-by: Jack Baldry <[email protected]> * Move k6 docs to subdirectory Signed-off-by: Jack Baldry <[email protected]> * Update script example Signed-off-by: Jack Baldry <[email protected]> * Add k6-studio to Makefile Signed-off-by: Jack Baldry <[email protected]> * Fix doc-validator for k6 Signed-off-by: Jack Baldry <[email protected]> * Use awk not grep Signed-off-by: Jack Baldry <[email protected]> --------- Signed-off-by: Jack Baldry <[email protected]>
…to hts/k6-studio
Llandy3d
approved these changes
Oct 28, 2024
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.
What?
Add the k6 Studio documentation to k6-docs.
This PR breaks up the publishing workflows, and adds a couple of pages for the k6 Studio docs.
Checklist
npm startcommand locally and verified that the changes look good.docs/sources/nextfolder of the documentation.docs/sources/v{most_recent_release}folder of the documentation.Related PR(s)/Issue(s)