update cli, gh action, and docs to include all features #47
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
|
Woops, forgot to run pre-commit. Just did that. |
|
Running into an actual issue this time. 
This started happening when I added I wonder if we can just add a |
|
Never mind the Also, give this PR a few minutes... I'm making some more changes. |
|
Ready for re-review! |
ewels
approved these changes
Apr 28, 2024
|
|
||
| 1. Install the [VSCode-YAML extension](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml) | ||
|
|
||
| 2. In your repo, create a `.vscode/settings.jsonc` or `.vscode/settings.template.jsonc` file containing the following data. This is what tells the extension which schema to associate with each file. |
There was a problem hiding this comment.
We should add this to https://www.schemastore.org/json/ so that it loads automatically for any VSCode users.
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.
I'm updating
rich-clickdocs right now.Having
working_dir:as an option in the Github Actions would be extremely helpful. For now I need to do either<!-- RICH-CODEX working_dir: . -->or use afake_commandon literally every command in the docs to make it work the way I want. Addingworking_dir: "."to the GH action would be great.While I was at it, I also updated the table to reflect everything available in the CLI, as I noticed it wasn't in parity.
Update: won't use these for rich-click docs after all, but they're still good changes.