-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
README: link out to the excellent testifylint #1568
Conversation
Cc: @Antonboom for review |
@brackendawson It would be good to also link to testifylint from the packages documentations for more visibility. |
I checked the render locally.
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.
Thank you, guys!
Appreciated.
For readers this PR, welcome to contribution 🙏
https://github.com/Antonboom/testifylint/blob/master/CONTRIBUTING.md#open-for-contribution
Co-authored-by: Olivier Mengué <dolmen@cpan.org>
Summary
Add a call to action to the README to use testifylint.
Changes
Motivation
Testify has many pitfalls due to the quality of some parts of the API, a lot of these cannot be fixed in testify without breaking the Go modules compatibility promise. testifylint can warn users when they fall in these pits.