From 8e2b1d88bbd24d8ed32adcab712c1d2c0d261adb Mon Sep 17 00:00:00 2001 From: Jonas Kuske <30421456+jonaskuske@users.noreply.github.com> Date: Sun, 31 May 2020 19:07:28 +0200 Subject: [PATCH] docs: add link to further information on linting --- .github/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 23d10c1..4c3783e 100755 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -86,7 +86,7 @@ A few general rules of thumb about what makes a good pull request: - Make small commits with clear and explainful messages - Provide a clear description about your contribution on GitHub -When you commit code, Water.css will run some checks to make sure that your changes have no errors and match the project's coding style – a process called **Linting**. It will also verify that all **colors are accessible**, which means they need to have enough contrast to be easily readable. +When you commit code, Water.css will run some checks to make sure that your changes have no errors and match the project's coding style – a process called [**Linting**](https://www.freecodecamp.org/news/what-is-linting-and-how-can-it-save-you-time). It will also verify that all **colors are accessible**, which means they need to have enough contrast to be easily readable. If the code you introduced has errors or some of the colors aren't accessible, you'll see an error and the commit will abort. You can check whether your changes pass all tests before committing them by running: