mirror_css/css-water.css
1
0
Fork 0
mirror of https://github.com/kognise/water.css.git synced 2025-08-11 15:45:15 +02:00
Code Issues Releases Wiki Activity

docs: add link to further information on linting

Browse Source
This commit is contained in:
Jonas Kuske
2020-05-31 19:07:28 +02:00
parent 1a14ad2652
commit 8e2b1d88bb
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.github/CONTRIBUTING.md vendored
View File

@@ -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 - Make small commits with clear and explainful messages
- Provide a clear description about your contribution on GitHub - 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. 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: You can check whether your changes pass all tests before committing them by running: