summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThong Kuah <tkuah@gitlab.com>2019-09-02 02:35:13 +0000
committerThong Kuah <tkuah@gitlab.com>2019-09-02 02:35:13 +0000
commit15497a0e54346893c43dcf659bbde2de423f075c (patch)
tree587428247730fb4a7a570dbabefe9a4718e9e695
parentc4db0483c9915c947198c9672abb2ccfaeab5719 (diff)
downloadgitlab-ce-add-overcommit-support.tar.gz
Apply suggestion to doc/development/contributing/style_guides.mdadd-overcommit-support
-rw-r--r--doc/development/contributing/style_guides.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/contributing/style_guides.md b/doc/development/contributing/style_guides.md
index 597b23069c3..f825b3d7088 100644
--- a/doc/development/contributing/style_guides.md
+++ b/doc/development/contributing/style_guides.md
@@ -30,7 +30,7 @@
This is also the style used by linting tools such as
[RuboCop](https://github.com/rubocop-hq/rubocop) and [Hound CI](https://houndci.com).
You can run RuboCop by hand or install a tool like [Overcommit](https://github.com/sds/overcommit) to run it for you.
-`Overcommit will automatically run the configured checks (like Rubocop) on every modified file before commit. You can use the example overcommit configuration found in `.overcommit.yml.example` as a quickstart.
+Overcommit will automatically run the configured checks (like Rubocop) on every modified file before commit. You can use the example overcommit configuration found in `.overcommit.yml.example` as a quickstart.
This saves you time as you don't have to wait for the same errors to be detected by the CI.
---