Add Documention for pest-plugin-profanity
#312
Conversation
This file contains hidden or 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
owenvoke
reviewed
May 24, 2025
Co-authored-by: Owen Voke <development@voke.dev>
|
Thanks @owenvoke - You wouldn't think I re-read it like 5 times before I put the PR in 😆 |
owenvoke
approved these changes
May 24, 2025
|
Hey @owenvoke Do you know the process for getting screenshots onto documentation? |
|
@JonPurvis, unsure. 🤔 I'd assume @nunomaduro adds them manually? |
This is the image, I've updated the markdown file to reference |
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.
This PR adds documentation for the Pest Profanity Plugin.
The only thing I need to do is update the screenshot as it's still showing the screenshot for Type Coverage. It looks like screenshots are stored outside of this repo.