-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move vale configs into docs/
#47575
Move vale configs into docs/
#47575
Conversation
58c3cc5
to
0db6e2a
Compare
🤖 Vercel preview here: https://docs-29a7uqg7v-goteleport.vercel.app/docs/ver/preview |
🤖 Vercel preview here: https://docs-dwwbp2m4t-goteleport.vercel.app/docs/ver/preview |
🤖 Vercel preview here: https://docs-5tczedhgu-goteleport.vercel.app/docs/ver/preview |
Organize vale prose linter configurations into the `docs` directory so automated workflows treat them as Teleport documentation changes. Otherwise, vale style changes are classified as code changes, which is not correct.
bbe9a07
to
c4d64c4
Compare
Here is a run of the vale check with a test page that fails as expected: https://github.com/gravitational/teleport/actions/runs/11351096747/job/31570965899?pr=47575 I removed the test page in this commit. |
🤖 Vercel preview here: https://docs-h51wgawzy-goteleport.vercel.app/docs/ver/preview |
@mmcallister Would you have time to give this a look? Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bot
Organize vale prose linter configurations into the
docs
directory so automated workflows treat them as Teleport documentation changes. Otherwise, vale style changes are classified as code changes, which is not correct.