Add latest changes from gitlab-org/gitlab@master

4 files changed, 29 insertions, 29 deletions

diff --git a/doc/administration/raketasks/check.md b/doc/administration/raketasks/check.md
index eb230f02c0d..7f3405df060 100644
--- a/doc/administration/raketasks/check.md
+++ b/doc/administration/raketasks/check.md
@@ -33,7 +33,7 @@ integrity check described previously.
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake gitlab:git:fsck
 ```
 
@@ -58,7 +58,7 @@ Currently, integrity checks are supported for the following types of file:
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake gitlab:artifacts:check
 sudo gitlab-rake gitlab:lfs:check
 sudo gitlab-rake gitlab:uploads:check
@@ -90,7 +90,7 @@ sudo gitlab-rake gitlab:uploads:check BATCH=100 ID_FROM=50 ID_TO=250
 
 Example output:
 
-```
+```bash
 $ sudo gitlab-rake gitlab:uploads:check
 Checking integrity of Uploads
 - 1..1350: Failures: 0
@@ -107,7 +107,7 @@ Done!
 
 Example verbose output:
 
-```
+```bash
 $ sudo gitlab-rake gitlab:uploads:check VERBOSE=1
 Checking integrity of Uploads
 - 1..1350: Failures: 0
diff --git a/doc/administration/raketasks/geo.md b/doc/administration/raketasks/geo.md
index 09f72c3411d..8bf720d2872 100644
--- a/doc/administration/raketasks/geo.md
+++ b/doc/administration/raketasks/geo.md
@@ -11,7 +11,7 @@ This is equivalent of running `git repack -d` on a _bare_ repository.
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake geo:git:housekeeping:incremental_repack
 ```
 
@@ -29,7 +29,7 @@ when this is enabled in GitLab.
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake geo:git:housekeeping:full_repack
 ```
 
@@ -46,7 +46,7 @@ a reachability bitmap index when this is enabled in GitLab.
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake geo:git:housekeeping:gc
 ```
 
@@ -63,7 +63,7 @@ can remove them using the rake task `geo:run_orphaned_project_registry_cleaner`:
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake geo:run_orphaned_project_registry_cleaner
 ```
 
diff --git a/doc/administration/raketasks/ldap.md b/doc/administration/raketasks/ldap.md
index 36db98a2102..41a9a4192cf 100644
--- a/doc/administration/raketasks/ldap.md
+++ b/doc/administration/raketasks/ldap.md
@@ -9,7 +9,7 @@ using the command below.
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake gitlab:ldap:check
 ```
 
@@ -41,7 +41,7 @@ instead.
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake gitlab:ldap:group_sync
 ```
 
@@ -101,7 +101,7 @@ sudo gitlab-rake gitlab:ldap:rename_provider[ldapmain,ldapmycompany]
 
 Example output:
 
-```
+```plaintext
 100 users with provider 'ldapmain' will be updated to 'ldapmycompany'.
 If the new provider is incorrect, users will be unable to sign in.
 Do you want to continue (yes/no)? yes
@@ -128,7 +128,7 @@ bundle exec rake gitlab:ldap:rename_provider RAILS_ENV=production
 
 **Example output:**
 
-```
+```plaintext
 What is the old provider? Ex. 'ldapmain': ldapmain
 What is the new provider? Ex. 'ldapcustom': ldapmycompany
 ```
diff --git a/doc/administration/raketasks/maintenance.md b/doc/administration/raketasks/maintenance.md
index 149b8d62309..efc7a84a80e 100644
--- a/doc/administration/raketasks/maintenance.md
+++ b/doc/administration/raketasks/maintenance.md
@@ -6,19 +6,19 @@ This command gathers information about your GitLab installation and the System i
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake gitlab:env:info
 ```
 
 **Source Installation**
 
-```
+```bash
 bundle exec rake gitlab:env:info RAILS_ENV=production
 ```
 
 Example output:
 
-```
+```plaintext
 System information
 System:           Debian 7.8
 Current User:     git
@@ -66,13 +66,13 @@ You may also have a look at our Troubleshooting Guides:
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake gitlab:check
 ```
 
 **Source Installation**
 
-```
+```bash
 bundle exec rake gitlab:check RAILS_ENV=production
 ```
 
@@ -80,7 +80,7 @@ NOTE: Use `SANITIZE=true` for `gitlab:check` if you want to omit project names f
 
 Example output:
 
-```
+```plaintext
 Checking Environment ...
 
 Git configured for git user? ... yes
@@ -129,18 +129,18 @@ In some case it is necessary to rebuild the `authorized_keys` file.
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake gitlab:shell:setup
 ```
 
 **Source Installation**
 
-```
+```bash
 cd /home/git/gitlab
 sudo -u git -H bundle exec rake gitlab:shell:setup RAILS_ENV=production
 ```
 
-```
+```plaintext
 This will rebuild an authorized_keys file.
 You will lose any data stored in authorized_keys file.
 Do you want to continue (yes/no)? yes
@@ -153,13 +153,13 @@ clear Redis' cache.
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake cache:clear
 ```
 
 **Source Installation**
 
-```
+```bash
 cd /home/git/gitlab
 sudo -u git -H bundle exec rake cache:clear RAILS_ENV=production
 ```
@@ -174,7 +174,7 @@ Omnibus packages.
 
 **Source Installation**
 
-```
+```bash
 cd /home/git/gitlab
 sudo -u git -H bundle exec rake gitlab:assets:compile RAILS_ENV=production
 ```
@@ -194,13 +194,13 @@ in the GitLab Performance Monitoring database.
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake gitlab:track_deployment
 ```
 
 **Source Installation**
 
-```
+```bash
 cd /home/git/gitlab
 sudo -u git -H bundle exec rake gitlab:track_deployment RAILS_ENV=production
 ```
@@ -213,13 +213,13 @@ is included to help you with this:
 
 **Omnibus Installation**
 
-```
+```bash
 sudo gitlab-rake gitlab:tcp_check[example.com,80]
 ```
 
 **Source Installation**
 
-```
+```bash
 cd /home/git/gitlab
 sudo -u git -H bundle exec rake gitlab:tcp_check[example.com,80] RAILS_ENV=production
 ```
@@ -279,6 +279,6 @@ This could be as a result of [updating existing metrics](../../development/prome
 
 To re-import the metrics you can run:
 
-```sh
+```bash
 sudo gitlab-rake metrics:setup_common_metrics
 ```