You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## 🧰 Changes
noticed our TOC looks a lil off at the moment:
<img width="1656" height="572" alt="CleanShot 2025-08-12 at 11 30 00@2x"
src="https://github.com/user-attachments/assets/eef159df-1845-42ea-a77a-fca10ebfe485"
/>
turns out `oclif`'s autogenerated TOC generation was incorrectly
thinking a YAML comment was a header. this fixes that!
*[Required in order for the GitHub Action to access your repo's contents](#required-in-order-for-the-github-action-to-access-your-repos-contents)
44
-
*[Runs the `rdme openapi validate petstore.json` command with the root directory being your repo](#runs-the-rdme-openapi-validate-petstorejson-command-with-the-root-directory-being-your-repo)
45
43
*[Command Topics](#command-topics)
46
44
<!-- tocstop -->
47
45
<!-- prettier-ignore-end -->
@@ -147,10 +145,10 @@ rdme login
147
145
`rdme` has a thin wrapper that allows the CLI to be used as a proper action in a GitHub Actions workflow. For example, say you wanted to run `rdme openapi validate petstore.json` in a GitHub Actions environment. Here's what the corresponding steps would look like in a GitHub Actions workflow file:
148
146
149
147
```yml
150
-
# Required in order for the GitHub Action to access your repo's contents
148
+
## Required in order for the GitHub Action to access your repo's contents
151
149
- uses: actions/checkout@v4
152
150
153
-
# Runs the `rdme openapi validate petstore.json` command with the root directory being your repo
151
+
## Runs the `rdme openapi validate petstore.json` command with the root directory being your repo
0 commit comments