Clarify that black runs with --safe by default #3378
Merged
Conversation
This file contains 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
|
Could you fix the lint issue by reformatting with prettier? |
|
Sorry, I made the changes on the GitHub page in the browser, saw the error but did not come around to fix the mishap. Should have stuck to the contributing workflow properly. My bad. Done now! |
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.
fixes #3375
Description
The docs had ambiguity about the
--safeflag as pointed out in #3375. This PR improves the clarity of the docs.Checklist - did you ...
CHANGES.mdif necessary?I don't think this needs to be noted in
CHANGES.md. Of course, I can if it is desired.