Hacker News new | past | comments | ask | show | jobs | submit login

I wonder how well this works. Word blacklists tend to be very crude tools.

For example, how often must people actively spend effort working around all the blocked past tense forms? How do you express that something used to work differently in a previous version under these restrictions?




Our docs are on github. We enabled Travis CI checks and all commits are now automatically validated with the default and custom markdownlint rules. If the linter finds errors, the committer receives a warning to Rocket chat with a link to Travis CI status page containing errors as well as suggestions on how to fix them.


"Remember that everything in this guide is a guideline, not a draconian rule."

The context makes it clear that it is future tense which should be avoided when describing system behavior.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: