Merge branch 'check-css' into 'master'

Check Css Based on Dmitriy his remark https://gitlab.slack.com/archives/general/p1395770459000142

Merge branch 'check-css' into 'master'
Check Css Based on Dmitriy his remark https://gitlab.slack.com/archives/general/p1395770459000142
Dmitriy Zaporozhets
2 parents 7ddbc92a 5bda665d
Showing 1 changed file with 1 additions and 0 deletions Show diff stats
CONTRIBUTING.md
@@ -67,6 +67,7 @@ If you can, please submit a merge request with the fix or improvements including
 1. The MR title should describes the change you want to make
 1. The MR description should give a motive for your change and the method you used to achieve it
 1. If the MR changes the UI it should include before and after screenshots
+1. If the MR changes CSS classes please include the list of affected pages `grep css-class ./app -R`
 1. Link relevant [issues](https://gitlab.com/gitlab-org/gitlab-ce/issues) and/or [feature requests](http://feedback.gitlab.com/) from the merge request description and leave a comment on them with a link back to the MR
 1. Be prepared to answer questions and incorporate feedback even if requests for this arrive weeks or months after your MR submittion
 1. If your MR touches code that executes shell commands, make sure it adheres to the [shell command guidelines](    doc/development/shell_commands.md).
...	...	@@ -67,6 +67,7 @@ If you can, please submit a merge request with the fix or improvements including
67	67	1. The MR title should describes the change you want to make
68	68	1. The MR description should give a motive for your change and the method you used to achieve it
69	69	1. If the MR changes the UI it should include before and after screenshots
	70	+1. If the MR changes CSS classes please include the list of affected pages `grep css-class ./app -R`
70	71	1. Link relevant [issues](https://gitlab.com/gitlab-org/gitlab-ce/issues) and/or [feature requests](http://feedback.gitlab.com/) from the merge request description and leave a comment on them with a link back to the MR
71	72	1. Be prepared to answer questions and incorporate feedback even if requests for this arrive weeks or months after your MR submittion
72	73	1. If your MR touches code that executes shell commands, make sure it adheres to the [shell command guidelines]( doc/development/shell_commands.md).
...	...