diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-31 12:08:09 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-31 12:08:09 +0000 |
commit | 0d0cddc9ce20c5a7d8a2723d0aa620ca184a711a (patch) | |
tree | 64f91b4d4ca74aa09d2a62ac5910820d087ed7cb /doc/administration/file_hooks.md | |
parent | 6044caed20964a70c1ac6c5a3365d567ed96dfde (diff) | |
download | gitlab-ce-0d0cddc9ce20c5a7d8a2723d0aa620ca184a711a.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/file_hooks.md')
-rw-r--r-- | doc/administration/file_hooks.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/administration/file_hooks.md b/doc/administration/file_hooks.md index dbcc37b25e7..60bfca74b6b 100644 --- a/doc/administration/file_hooks.md +++ b/doc/administration/file_hooks.md @@ -88,9 +88,9 @@ end ## Validation Writing your own file hook can be tricky and it's easier if you can check it -without altering the system. A rake task is provided so that you can use it +without altering the system. A Rake task is provided so that you can use it in a staging environment to test your file hook before using it in production. -The rake task will use a sample data and execute each of file hook. The output +The Rake task will use a sample data and execute each of file hook. The output should be enough to determine if the system sees your file hook and if it was executed without errors. |