Skip to content
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

read/write should not trigger the slash rule + adjust scope for Slash.yml #714

Merged
merged 1 commit into from
Feb 12, 2024

Conversation

aireilly
Copy link
Member

@aireilly aireilly commented Feb 9, 2024

No description provided.

Copy link

github-actions bot commented Feb 9, 2024

Click here to review and test in web IDE: Contribute

Copy link

github-actions bot commented Feb 9, 2024

🎊 Navigate the preview: https://redhat-documentation-vale-at-red-hat-714.surge.sh 🎊

@aireilly aireilly force-pushed the adjust-slash branch 3 times, most recently from 1fdd816 to 2cf3a7b Compare February 9, 2024 14:58
@aireilly aireilly changed the title read/write should not trigger the slash rule read/write should not trigger the slash rule + adjust scope for CaseSensitiveTerms.yml and Slash.yml Feb 9, 2024
@aireilly aireilly force-pushed the adjust-slash branch 3 times, most recently from 78ff3d0 to 0832bc5 Compare February 9, 2024 17:31
Copy link
Collaborator

@rohennes rohennes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do the additions to the Slash rule need to be added in the testvalid.adoc fixture? Otherwise looks good to me

@aireilly aireilly force-pushed the adjust-slash branch 3 times, most recently from 1eb0615 to 58bebda Compare February 12, 2024 10:42
@aireilly aireilly changed the title read/write should not trigger the slash rule + adjust scope for CaseSensitiveTerms.yml and Slash.yml read/write should not trigger the slash rule + adjust scope for Slash.yml Feb 12, 2024
@aireilly aireilly merged commit 284c616 into redhat-documentation:main Feb 12, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants