-
Notifications
You must be signed in to change notification settings - Fork 36
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
chore: add vale rule to enforce colon usage #2441
Conversation
✅ Deploy Preview for docs-spectrocloud ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -337,7 +337,7 @@ stages: | |||
|
|||
#### Invoke Custom Script | |||
|
|||
An example of applying logic after the device has booted by using the `boot.after` stage. <br /> | |||
An example of applying logic after the device has booted by using the `boot.after` stage: |
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.
🚫 [vale] reported by reviewdog 🐶
[spectrocloud.colon] Use colons only to introduce lists, unless in code blocks or inline code.
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.
Yay - this is working as intended
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.
I tested it and it looks great
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
🎉 This PR is included in version 4.2.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 4.2.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Describe the Change
This PR ensures that colons are only used to introduce a list. It specifically looks for a colon, followed by two new line characters, and then any character that is not a dash or a new line. I think this is also the most frequent mistake for us which is to introduce a command with a colon.
It does not try to catch instances of inline colon usage such as
There are three kinds of apples: fuji, honey crisp, and cosmic crisp
, which I think is permissible and avoids flagging all the false positives in code blocks.It is possible that this rule could lead to some false positives in code snippets, but there should be only very few of these, and i think we can usually remove the extra new line character if they occur.
Changed Pages
N/A
Jira Tickets
🎫 DOC-1114
Backports
Can this PR be backported?