Add latest changes from gitlab-org/gitlab@master

536aa3a1 · GitLab Bot · 50ae4065 · 536aa3a1 · 536aa3a1 · 536aa3a1
Commit 536aa3a1 authored 5 years ago by GitLab Bot
--- a/doc/administration/raketasks/uploads/sanitize.md
+++ b/doc/administration/raketasks/uploads/sanitize.md
@@ -7,7 +7,7 @@ You need `exiftool` installed on your system. If you installed GitLab:
 - Using the Omnibus package, you're all set.
 - From source, make sure `exiftool` is installed:
  
-  ```sh
+  ```shell
  # Debian/Ubuntu
  sudo apt-get install libimage-exiftool-perl
  
@@ -22,7 +22,7 @@ Because EXIF data may contain sensitive information (e.g. GPS location), you
 can remove EXIF data also from existing images which were uploaded before
 with the following command:
  
-```bash
+```shell
 sudo RAILS_ENV=production -u git -H bundle exec rake gitlab:uploads:sanitize:remove_exif
 ```
  
@@ -46,13 +46,13 @@ each with a separate range of upload IDs (by setting `start_id` and `stop_id`).
  
 To run the command without dry mode and remove EXIF data from all uploads, you can use:
  
-```bash
+```shell
 sudo RAILS_ENV=production -u git -H bundle exec rake gitlab:uploads:sanitize:remove_exif[,,false,] 2>&1 | tee exif.log
 ```
  
 To run the command without dry mode on uploads with ID between 100 and 5000 and pause for 0.1 second, you can use:
  
-```bash
+```shell
 sudo RAILS_ENV=production -u git -H bundle exec rake gitlab:uploads:sanitize:remove_exif[100,5000,false,0.1] 2>&1 | tee exif.log
 ```
  

--- a/doc/administration/reply_by_email_postfix_setup.md
+++ b/doc/administration/reply_by_email_postfix_setup.md
@@ -14,7 +14,7 @@ The instructions make the assumption that you will be using the email address `i
  
 1. Install the `postfix` package if it is not installed already:
  
-   ```sh
+   ```shell
   sudo apt-get install postfix
   ```
  
@@ -22,7 +22,7 @@ The instructions make the assumption that you will be using the email address `i
  
 1. Install the `mailutils` package.
  
-   ```sh
+   ```shell
   sudo apt-get install mailutils
   ```
  
@@ -30,13 +30,13 @@ The instructions make the assumption that you will be using the email address `i
  
 1. Create a user for incoming email.
  
-   ```sh
+   ```shell
   sudo useradd -m -s /bin/bash incoming
   ```
  
 1. Set a password for this user.
  
-   ```sh
+   ```shell
   sudo passwd incoming
   ```
  
@@ -46,13 +46,13 @@ The instructions make the assumption that you will be using the email address `i
  
 1. Connect to the local SMTP server:
  
-   ```sh
+   ```shell
   telnet localhost 25
   ```
  
   You should see a prompt like this:
  
-   ```sh
+   ```shell
   Trying 127.0.0.1...
   Connected to localhost.
   Escape character is '^]'.
@@ -61,13 +61,13 @@ The instructions make the assumption that you will be using the email address `i
  
   If you get a `Connection refused` error instead, verify that `postfix` is running:
  
-   ```sh
+   ```shell
   sudo postfix status
   ```
  
   If it is not, start it:
  
-   ```sh
+   ```shell
   sudo postfix start
   ```
  
@@ -94,7 +94,7 @@ The instructions make the assumption that you will be using the email address `i
  
 1. Check if the `incoming` user received the email:
  
-   ```sh
+   ```shell
   su - incoming
   mail
   ```
@@ -108,13 +108,13 @@ The instructions make the assumption that you will be using the email address `i
  
   Quit the mail app:
  
-   ```sh
+   ```shell
   q
   ```
  
 1. Log out of the `incoming` account and go back to being `root`:
  
-   ```sh
+   ```shell
   logout
   ```
  
@@ -124,13 +124,13 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
  
 1. Configure Postfix to use Maildir-style mailboxes:
  
-   ```sh
+   ```shell
   sudo postconf -e "home_mailbox = Maildir/"
   ```
  
 1. Restart Postfix:
  
-   ```sh
+   ```shell
   sudo /etc/init.d/postfix restart
   ```
  
@@ -139,7 +139,7 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
   1. Follow steps 1 and 2 of _[Test the out-of-the-box setup](#test-the-out-of-the-box-setup)_.
   1. Check if the `incoming` user received the email:
  
-      ```sh
+      ```shell
      su - incoming
      MAIL=/home/incoming/Maildir
      mail
@@ -154,7 +154,7 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
  
      Quit the mail app:
  
-      ```sh
+      ```shell
      q
      ```
  
@@ -166,7 +166,7 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
  
 1. Log out of the `incoming` account and go back to being `root`:
  
-   ```sh
+   ```shell
   logout
   ```
  
@@ -174,25 +174,25 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
  
 1. Install the `courier-imap` package:
  
-   ```sh
+   ```shell
   sudo apt-get install courier-imap
   ```
  
   And start `imapd`:
  
-   ```sh
+   ```shell
   imapd start
   ```
  
 1. The courier-authdaemon isn't started after installation. Without it, imap authentication will fail:
  
-   ```sh
+   ```shell
   sudo service courier-authdaemon start
   ```
  
   You can also configure courier-authdaemon to start on boot:
  
-   ```sh
+   ```shell
   sudo systemctl enable courier-authdaemon
   ```
  
@@ -200,7 +200,7 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
  
 1. Let Postfix know about the domains that it should consider local:
  
-   ```sh
+   ```shell
   sudo postconf -e "mydestination = gitlab.example.com, localhost.localdomain, localhost"
   ```
  
@@ -208,25 +208,25 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
  
   We'll assume `192.168.1.0/24` is your local LAN. You can safely skip this step if you don't have other machines in the same local network.
  
-   ```sh
+   ```shell
   sudo postconf -e "mynetworks = 127.0.0.0/8, 192.168.1.0/24"
   ```
  
 1. Configure Postfix to receive mail on all interfaces, which includes the internet:
  
-   ```sh
+   ```shell
   sudo postconf -e "inet_interfaces = all"
   ```
  
 1. Configure Postfix to use the `+` delimiter for sub-addressing:
  
-   ```sh
+   ```shell
   sudo postconf -e "recipient_delimiter = +"
   ```
  
 1. Restart Postfix:
  
-   ```sh
+   ```shell
   sudo service postfix restart
   ```
  
@@ -236,13 +236,13 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
  
   1. Connect to the SMTP server:
  
-      ```sh
+      ```shell
      telnet gitlab.example.com 25
      ```
  
      You should see a prompt like this:
  
-      ```sh
+      ```shell
      Trying 123.123.123.123...
      Connected to gitlab.example.com.
      Escape character is '^]'.
@@ -269,7 +269,7 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
  
   1. Check if the `incoming` user received the email:
  
-      ```sh
+      ```shell
      su - incoming
      MAIL=/home/incoming/Maildir
      mail
@@ -284,13 +284,13 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
  
      Quit the mail app:
  
-      ```sh
+      ```shell
      q
      ```
  
   1. Log out of the `incoming` account and go back to being `root`:
  
-      ```sh
+      ```shell
      logout
      ```
  
@@ -298,13 +298,13 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
  
   1. Connect to the IMAP server:
  
-      ```sh
+      ```shell
      telnet gitlab.example.com 143
      ```
  
      You should see a prompt like this:
  
-      ```sh
+      ```shell
      Trying 123.123.123.123...
      Connected to mail.example.gitlab.com.
      Escape character is '^]'.
@@ -327,7 +327,7 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
  
   1. Disconnect from the IMAP server:
  
-      ```sh
+      ```shell
      a logout
      ```
  

--- a/doc/administration/repository_storage_types.md
+++ b/doc/administration/repository_storage_types.md
@@ -118,7 +118,7 @@ to validate. You can do so by specifying a range with the operation.
 This is an example of how to limit the rollout to Project IDs 50 to 100, running in
 an Omnibus GitLab installation:
  
-```bash
+```shell
 sudo gitlab-rake gitlab:storage:migrate_to_hashed ID_FROM=50 ID_TO=100
 ```
  
@@ -139,7 +139,7 @@ To schedule a complete rollback, see the
 The rollback task also supports specifying a range of Project IDs. Here is an example
 of limiting the rollout to Project IDs 50 to 100, in an Omnibus GitLab installation:
  
-```bash
+```shell
 sudo gitlab-rake gitlab:storage:rollback_to_legacy ID_FROM=50 ID_TO=100
 ```
  

--- a/doc/administration/restart_gitlab.md
+++ b/doc/administration/restart_gitlab.md
@@ -31,7 +31,7 @@ GitLab Rails application (Unicorn) as well as the other components, like:
 There may be times in the documentation where you will be asked to _restart_
 GitLab. In that case, you need to run the following command:
  
-```bash
+```shell
 sudo gitlab-ctl restart
 ```
  
@@ -51,13 +51,13 @@ ok: run: unicorn: (pid 11338) 0s
 To restart a component separately, you can append its service name to the
 `restart` command. For example, to restart **only** NGINX you would run:
  
-```bash
+```shell
 sudo gitlab-ctl restart nginx
 ```
  
 To check the status of GitLab services, run:
  
-```bash
+```shell
 sudo gitlab-ctl status
 ```
  
@@ -79,7 +79,7 @@ GitLab. Remember that this method applies only for the Omnibus packages.
  
 Reconfigure Omnibus GitLab with:
  
-```bash
+```shell
 sudo gitlab-ctl reconfigure
 ```
  
@@ -152,7 +152,7 @@ the [cloud native Helm Chart](https://docs.gitlab.com/charts/). Usually, it shou
 enough to restart a specific component separately (`gitaly`, `unicorn`,
 `workhorse`, `gitlab-shell`, etc.) by deleting all the pods related to it:
  
-```bash
+```shell
 kubectl delete pods -l release=<helm release name>,app=<component name>
 ```
  

--- a/doc/administration/server_hooks.md
+++ b/doc/administration/server_hooks.md
@@ -111,7 +111,7 @@ declined or an error occurs during the Git hook, your script should:
  
 This hook script written in bash will generate the following message in GitLab's UI:
  
-```bash
+```shell
 #!/bin/sh
 echo "GL-HOOK-ERR: My custom error message.";
 exit 1

--- a/doc/administration/smime_signing_email.md
+++ b/doc/administration/smime_signing_email.md
@@ -67,7 +67,7 @@ extensions), which contain the following in a single encrypted file:
 In order to export the required files in PEM encoding from the PKCS#12 file,
 the `openssl` command can be used:
  
-```bash
+```shell
 #-- Extract private key in PEM encoding (no password, unencrypted)
 $ openssl pkcs12 -in gitlab.p12 -nocerts -nodes -out gitlab.key
  

--- a/doc/administration/snippets/index.md
+++ b/doc/administration/snippets/index.md
@@ -35,7 +35,7 @@ The steps to configure this setting through the Rails console are:
  
 1. Start the Rails console:
  
-   ```bash
+   ```shell
   # For Omnibus installations
   sudo gitlab-rails console
  
@@ -60,12 +60,12 @@ To retrieve the current value, start the Rails console and run:
 The process to set the snippets size limit through the Application Settings API is
 exactly the same as you would do to [update any other setting](../../api/settings.md#change-application-settings).
  
-```bash
+```shell
 curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/settings?snippet_size_limit=52428800
 ```
  
 You can also use the API to [retrieve the current value](../../api/settings.md#get-current-application-settings).
  
-```bash
+```shell
 curl --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/settings
 ```
--- a/doc/administration/timezone.md
+++ b/doc/administration/timezone.md
@@ -31,7 +31,7 @@ gitlab_rails['time_zone'] = 'America/New_York'
  
 After adding the configuration parameter, reconfigure and restart your GitLab instance:
  
-```sh
+```shell
 gitlab-ctl reconfigure
 gitlab-ctl restart
 ```
--- a/doc/administration/troubleshooting/debug.md
+++ b/doc/administration/troubleshooting/debug.md
@@ -10,13 +10,13 @@ an SMTP server, but you're not seeing mail delivered. Here's how to check the se
  
 1. Run a Rails console:
  
-   ```sh
+   ```shell
   sudo gitlab-rails console production
   ```
  
   or for source installs:
  
-   ```sh
+   ```shell
   bundle exec rails console production
   ```
  

--- a/doc/administration/troubleshooting/elasticsearch.md
+++ b/doc/administration/troubleshooting/elasticsearch.md
@@ -332,7 +332,7 @@ bind ports 9200/9300 so it can be used.
  
 The following is an example of running a docker container of Elasticsearch v7.2.0:
  
-```bash
+```shell
 docker pull docker.elastic.co/elasticsearch/elasticsearch:7.2.0
 docker run -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" docker.elastic.co/elasticsearch/elasticsearch:7.2.0
 ```

--- a/doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md
+++ b/doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md
@@ -30,7 +30,7 @@ should and, if needed, update the script for the latest version of GitLab.
 If the script you want to run is short, you can use the Rails Runner to avoid
 entering the rails console in the first place. Here's an example of its use:
  
-```bash
+```shell
 gitlab-rails runner "RAILS_COMMAND"
  
 # Example with a 2-line script
@@ -130,19 +130,19 @@ end
  
 ### Check the GitLab version fast
  
-```bash
+```shell
 grep -m 1 gitlab /opt/gitlab/version-manifest.txt
 ```
  
 ### Debugging SSH
  
-```bash
+```shell
 GIT_SSH_COMMAND="ssh -vvv" git clone <repository>
 ```
  
 ### Debugging over HTTPS
  
-```bash
+```shell
 GIT_CURL_VERBOSE=1 GIT_TRACE=1 git clone <repository>
 ```
  
@@ -301,19 +301,19 @@ correctly named empty project using the steps below.
  
 Move the new repository to the empty repository:
  
-```bash
+```shell
 mv /var/opt/gitlab/git-data/repositories/<group>/<new-project> /var/opt/gitlab/git-data/repositories/<group>/<empty-project>
 ```
  
 Make sure the permissions are correct:
  
-```bash
+```shell
 chown -R git:git <path-to-directory>.git
 ```
  
 Clear the cache:
  
-```bash
+```shell
 sudo gitlab-rake cache:clear
 ```
  
@@ -489,7 +489,7 @@ User.active.count
 ::HistoricalData.max_historical_user_count
 ```
  
-```bash
+```shell
 # Using curl and jq (up to a max 100, see pagination docs https://docs.gitlab.com/ee/api/#pagination
 curl --silent --header "Private-Token: ********************" "https://gitlab.example.com/api/v4/users?per_page=100&active" | jq --compact-output '.[] | [.id,.name,.username]'
 ```
@@ -995,13 +995,13 @@ See <https://github.com/mperham/sidekiq/wiki/Signals#ttin>.
  
 ### Connect to Redis (omnibus)
  
-```sh
+```shell
 /opt/gitlab/embedded/bin/redis-cli -s /var/opt/gitlab/redis/redis.socket
 ```
  
 ### Connect to Redis (HA)
  
-```sh
+```shell
 /opt/gitlab/embedded/bin/redis-cli -h <host ip> -a <password>
 ```
  
@@ -1034,7 +1034,7 @@ This script will go through all the encrypted variables and count how many are n
 to be decrypted. Might be helpful to run on multiple nodes to see which `gitlab-secrets.json`
 file is most up to date:
  
-```bash
+```shell
 wget -O /tmp/bad-decrypt.rb https://gitlab.com/snippets/1730735/raw
 gitlab-rails runner /tmp/bad-decrypt.rb
 ```
@@ -1075,7 +1075,7 @@ two-factor authentication.
 This script will search for all encrypted tokens that are causing decryption errors,
 and update or reset as needed:
  
-```bash
+```shell
 wget -O /tmp/encrypted-tokens.rb https://gitlab.com/snippets/1876342/raw
 gitlab-rails runner /tmp/encrypted-tokens.rb
 ```

--- a/doc/administration/troubleshooting/kubernetes_cheat_sheet.md
+++ b/doc/administration/troubleshooting/kubernetes_cheat_sheet.md
@@ -20,13 +20,13 @@ and they will assist you with any issues you are having.
 - How to authorize to your GCP project (can be especially useful if you have projects
  under different GCP accounts):
  
-  ```bash
+  ```shell
  gcloud auth login
  ```
  
 - How to access Kubernetes dashboard:
  
-  ```bash
+  ```shell
  # for minikube:
  minikube dashboard —url
  # for non-local installations if access via Kubectl is configured:
@@ -42,7 +42,7 @@ and they will assist you with any issues you are having.
  
 - How to copy a file from local machine to a pod:
  
-  ```bash
+  ```shell
  kubectl cp file-name pod-name:./destination-path
  ```
  
@@ -51,19 +51,19 @@ and they will assist you with any issues you are having.
  - Check logs via Kubernetes dashboard.
  - Check logs via Kubectl:
  
-    ```bash
+    ```shell
    kubectl logs <unicorn pod> -c dependencies
    ```
  
 - How to tail all Kubernetes cluster events in real time:
  
-  ```bash
+  ```shell
  kubectl get events -w --all-namespaces
  ```
  
 - How to get logs of the previously terminated pod instance:
  
-  ```bash
+  ```shell
  kubectl logs <pod-name> --previous
  ```
  
@@ -79,13 +79,13 @@ and they will assist you with any issues you are having.
  
 - Tailing logs of a separate pod. An example for a Unicorn pod:
  
-  ```bash
+  ```shell
  kubectl logs gitlab-unicorn-7656fdd6bf-jqzfs -c unicorn
  ```
  
 - Tail and follow all pods that share a label (in this case, `unicorn`):
  
-  ```bash
+  ```shell
  # all containers in the unicorn pods
  kubectl logs -f -l app=unicorn --all-containers=true --max-log-requests=50
  
@@ -96,21 +96,21 @@ and they will assist you with any issues you are having.
 - One can stream logs from all containers at once, similar to the Omnibus
  command `gitlab-ctl tail`:
  
-  ```bash
+  ```shell
  kubectl logs -f -l release=gitlab --all-containers=true --max-log-requests=100
  ```
  
 - Check all events in the `gitlab` namespace (the namespace name can be different if you
  specified a different one when deploying the Helm chart):
  
-  ```bash
+  ```shell
  kubectl get events -w --namespace=gitlab
  ```
  
 - Most of the useful GitLab tools (console, rake tasks, etc) are found in the task-runner
  pod. You may enter it and run commands inside or run them from the outside:
  
-  ```bash
+  ```shell
  # find the pod
  kubectl get pods | grep task-runner
  
@@ -145,7 +145,7 @@ and they will assist you with any issues you are having.
  
 - How to get your initial admin password <https://docs.gitlab.com/charts/installation/deployment.html#initial-login>:
  
-  ```bash
+  ```shell
  # find the name of the secret containing the password
  kubectl get secrets | grep initial-root
  # decode it
@@ -154,19 +154,19 @@ and they will assist you with any issues you are having.
  
 - How to connect to a GitLab Postgres database:
  
-  ```bash
+  ```shell
  kubectl exec -it <task-runner-pod-name> -- /srv/gitlab/bin/rails dbconsole -p
  ```
  
 - How to get info about Helm installation status:
  
-  ```bash
+  ```shell
  helm status name-of-installation
  ```
  
 - How to update GitLab installed using Helm Chart:
  
-  ```bash
+  ```shell
  helm repo upgrade
  
  # get current values and redirect them to yaml file (analogue of gitlab.rb values)
@@ -185,7 +185,7 @@ and they will assist you with any issues you are having.
  - Modify the `gitlab.yaml` file.
  - Run the following command to apply changes:
  
-    ```bash
+    ```shell
    helm upgrade <release name> <chart path> -f gitlab.yaml
    ```
  
@@ -197,20 +197,20 @@ to those documents for details.
  
 - Install Kubectl via Homebrew:
  
-  ```bash
+  ```shell
  brew install kubernetes-cli
  ```
  
 - Install Minikube via Homebrew:
  
-  ```bash
+  ```shell
  brew cask install minikube
  ```
  
 - Start Minikube and configure it. If Minikube cannot start, try running `minikube delete && minikube start`
  and repeat the steps:
  
-  ```bash
+  ```shell
  minikube start --cpus 3 --memory 8192 # minimum amount for GitLab to work
  minikube addons enable ingress
  minikube addons enable kube-dns
@@ -218,7 +218,7 @@ to those documents for details.
  
 - Install Helm via Homebrew and initialize it:
  
-  ```bash
+  ```shell
  brew install kubernetes-helm
  helm init --service-account tiller
  ```
@@ -231,7 +231,7 @@ to those documents for details.
  
 - Install the GitLab Helm Chart:
  
-  ```bash
+  ```shell
  helm repo add gitlab https://charts.gitlab.io
  helm install --name gitlab -f <path-to-yaml-file> gitlab/gitlab
  ```

--- a/doc/administration/troubleshooting/linux_cheat_sheet.md
+++ b/doc/administration/troubleshooting/linux_cheat_sheet.md
@@ -23,7 +23,7 @@ on. Contributions are welcome to help add them.
  
 ### Distro Information
  
-```bash
+```shell
 # Debian/Ubuntu
 uname -a
 lsb_release -a
@@ -38,14 +38,14 @@ cat /etc/os-release
  
 ### Shut down or Reboot
  
-```bash
+```shell
 shutdown -h now
 reboot
 ```
  
 ### Permissions
  
-```bash
+```shell
 # change the user:group ownership of a file/dir
 chown root:git <file_or_dir>
  
@@ -55,7 +55,7 @@ chmod u+x <file>
  
 ### Files & Dirs
  
-```bash
+```shell
 # create a new directory and all subdirectories
 mkdir -p dir/dir2/dir3
  
@@ -71,7 +71,7 @@ sed -i 's/original-text/new-text/g' <filename>
  
 ### See all set environment variables
  
-```bash
+```shell
 env
 ```
  
@@ -79,7 +79,7 @@ env
  
 ### File names
  
-```bash
+```shell
 # search for a file in a filesystem
 find . -name 'filename.rb' -print
  
@@ -95,7 +95,7 @@ history
  
 ### File contents
  
-```bash
+```shell
 # -B/A = show 2 lines before/after search_term
 grep -B 2 -A 2 search_term <filename>
  
@@ -114,7 +114,7 @@ fgrep -R string_pattern <filename or directory>
  
 ### CLI
  
-```bash
+```shell
 # View command history
 history
  
@@ -132,7 +132,7 @@ sudo !!
  
 ### Memory, Disk, & CPU usage
  
-```bash
+```shell
 # disk space info.  The '-h' gives the data in human-readable values
 df -h
  
@@ -157,7 +157,7 @@ top -o %CPU
  
 ### Strace
  
-```bash
+```shell
 # strace a process
 strace -tt -T -f -y -s 1024 -p <pid>
  
@@ -200,7 +200,7 @@ can also sort based on total time, # of syscalls made, PID #, and # of child pro
 using the `-S` or `--sort` flag. The number of results defaults to 25 processes, but
 can be changed using the `-c`/`--count` option.  See `--help` for full details.
  
-```sh
+```shell
 $ ./strace-parser strace.txt
  
 Top 25 PIDs
@@ -218,7 +218,7 @@ Based on the summary, you can then view the details of syscalls made by one or m
 procsses using the `-p`/`--pid` for a specific process, or `-s`/`--stats` flags for
 a sorted list. `--stats` takes the same sorting and count options as summary.
  
-```sh
+```shell
 $ ./strace-parse strace.text -p 6423
  
 PID 6423
@@ -274,7 +274,7 @@ small differences should not be considered significant.
  
 ### Ports
  
-```bash
+```shell
 # Find the programs that are listening on ports
 netstat -plnt
 ss -plnt
@@ -283,7 +283,7 @@ lsof -i -P | grep <port>
  
 ### Internet/DNS
  
-```bash
+```shell
 # Show domain IP address
 dig +short example.com
 nslookup example.com
@@ -302,7 +302,7 @@ curl --head --location https://example.com
  
 ## Package Management
  
-```bash
+```shell
 # Debian/Ubuntu
  
 # List packages
@@ -332,7 +332,7 @@ rpm -qa | grep <package>
  
 ## Logs
  
-```bash
+```shell
 # Print last lines in log file where 'n'
 # is the number of lines to print
 tail -n /path/to/log/file

--- a/doc/administration/troubleshooting/ssl.md
+++ b/doc/administration/troubleshooting/ssl.md
@@ -83,13 +83,13 @@ To fix this problem:
  
 If your GitLab instance is using a self-signed certificate, or the certificate is signed by an internal certificate authority (CA), you might run into the following errors when attempting to perform Git operations:
  
-```bash
+```shell
 $ git clone https://gitlab.domain.tld/group/project.git
 Cloning into 'project'...
 fatal: unable to access 'https://gitlab.domain.tld/group/project.git/': SSL certificate problem: self signed certificate
 ```
  
-```bash
+```shell
 $ git clone https://gitlab.domain.tld/group/project.git
 Cloning into 'project'...
 fatal: unable to access 'https://gitlab.domain.tld/group/project.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
@@ -107,6 +107,6 @@ To fix this problem:
  
  - Disable SSL verification in your Git client. Note that this intended as a temporary measure as it could be considered a **security risk**.
  
-    ```bash
+    ```shell
    git config --global http.sslVerify false
    ```
--- a/doc/administration/troubleshooting/test_environments.md
+++ b/doc/administration/troubleshooting/test_environments.md
@@ -37,7 +37,7 @@ you change a few things:
  
 For example, when the `docker-machine` host we want to use is `do-docker`:
  
-```sh
+```shell
 docker run --detach --name gitlab \
 --env GITLAB_OMNIBUS_CONFIG="external_url 'http://$(docker-machine ip do-docker)'; gitlab_rails['gitlab_shell_ssh_port'] = 2222;" \
 --hostname $(docker-machine ip do-docker) \
@@ -52,7 +52,7 @@ gitlab/gitlab-ee:11.5.3-ee.0
 We can use the [`test-saml-idp` Docker image](https://hub.docker.com/r/jamedjo/test-saml-idp)
 to do the work for us:
  
-```sh
+```shell
 docker run --name gitlab_saml -p 8080:8080 -p 8443:8443 \
 -e SIMPLESAMLPHP_SP_ENTITY_ID=<GITLAB_IP_OR_DOMAIN> \
 -e SIMPLESAMLPHP_SP_ASSERTION_CONSUMER_SERVICE=<GITLAB_IP_OR_DOMAIN>/users/auth/saml/callback \
@@ -93,7 +93,7 @@ See [the GDK SAML documentation](https://gitlab.com/gitlab-org/gitlab-developmen
  
 ### Elasticsearch
  
-```sh
+```shell
 docker run -d --name elasticsearch \
 -p 9200:9200 -p 9300:9300 \
 -e "discovery.type=single-node" \
@@ -110,7 +110,7 @@ on running PlantUML in Docker.
  
 ### Jira
  
-```sh
+```shell
 docker run -d -p 8081:8080 cptactionhank/atlassian-jira:latest
 ```
  
@@ -119,7 +119,7 @@ Jira license.
  
 ### Grafana
  
-```sh
+```shell
 docker run -d --name grafana -e "GF_SECURITY_ADMIN_PASSWORD=gitlab" -p 3000:3000 grafana/grafana
 ```
  

--- a/doc/api/README.md
+++ b/doc/api/README.md
@@ -335,7 +335,7 @@ resources you can pass the following parameters:
  
 In the example below, we list 50 [namespaces](namespaces.md) per page.
  
-```bash
+```shell
 curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/namespaces?per_page=50"
 ```
  
@@ -349,7 +349,7 @@ In the cURL example below, we limit the output to 3 items per page (`per_page=3`
 and we request the second page (`page=2`) of [comments](notes.md) of the issue
 with ID `8` which belongs to the project with ID `8`:
  
-```bash
+```shell
 curl --head --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/projects/8/issues/8/notes?per_page=3&page=2
 ```
  
@@ -409,7 +409,7 @@ This method is controlled by the following parameters:
  
 In the example below, we list 50 [projects](projects.md) per page, ordered by `id` ascending.
  
-```bash
+```shell
 curl --request GET --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects?pagination=keyset&per_page=50&order_by=id&sort=asc"
 ```
  
@@ -472,7 +472,7 @@ We can call the API with `array` and `hash` types parameters as shown below:
  
 `import_sources` is a parameter of type `array`:
  
-```bash
+```shell
 curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" \
 -d "import_sources[]=github" \
 -d "import_sources[]=bitbucket" \
@@ -483,7 +483,7 @@ https://gitlab.example.com/api/v4/some_endpoint
  
 `override_params` is a parameter of type `hash`:
  
-```bash
+```shell
 curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" \
 --form "namespace=email" \
 --form "path=impapi" \
@@ -497,7 +497,7 @@ https://gitlab.example.com/api/v4/projects/import
  
 `variables` is a parameter of type `array` containing hash key/value pairs `[{ 'key' => 'UPLOAD_TO_S3', 'value' => 'true' }]`:
  
-```bash
+```shell
 curl --globoff --request POST --header "PRIVATE-TOKEN: ********************" \
 "https://gitlab.example.com/api/v4/projects/169/pipeline?ref=master&variables[][key]=VAR1&variables[][value]=hello&variables[][key]=VAR2&variables[][value]=world"
  

--- a/doc/api/access_requests.md
+++ b/doc/api/access_requests.md
@@ -29,7 +29,7 @@ GET /projects/:id/access_requests
  
 Example request:
  
-```bash
+```shell
 curl --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/groups/:id/access_requests
 curl --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/projects/:id/access_requests
 ```
@@ -72,7 +72,7 @@ POST /projects/:id/access_requests
  
 Example request:
  
-```bash
+```shell
 curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/groups/:id/access_requests
 curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/projects/:id/access_requests
 ```
@@ -107,7 +107,7 @@ PUT /projects/:id/access_requests/:user_id/approve
  
 Example request:
  
-```bash
+```shell
 curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/groups/:id/access_requests/:user_id/approve?access_level=20
 curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/projects/:id/access_requests/:user_id/approve?access_level=20
 ```
@@ -141,7 +141,7 @@ DELETE /projects/:id/access_requests/:user_id
  
 Example request:
  
-```bash
+```shell
 curl --request DELETE --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/groups/:id/access_requests/:user_id
 curl --request DELETE --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/projects/:id/access_requests/:user_id
 ```
--- a/doc/api/appearance.md
+++ b/doc/api/appearance.md
@@ -13,7 +13,7 @@ List the current appearance configuration of the GitLab instance.
 GET /application/appearance
 ```
  
-```bash
+```shell
 curl --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/appearance
 ```
  
@@ -57,7 +57,7 @@ PUT /application/appearance
 | `message_font_color`              | string  | no       | Font color for the system header / footer bar
 | `email_header_and_footer_enabled` | boolean | no       | Add header and footer to all outgoing emails if enabled
  
-```bash
+```shell
 curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/application/appearance?email_header_and_footer_enabled=true&header_message=test
 ```
  

--- a/doc/api/applications.md
+++ b/doc/api/applications.md
@@ -31,7 +31,7 @@ Parameters:
  
 Example request:
  
-```sh
+```shell
 curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" --data "name=MyApplication&redirect_uri=http://redirect.uri&scopes=" https://gitlab.example.com/api/v4/applications
 ```
  
@@ -58,7 +58,7 @@ GET /applications
  
 Example request:
  
-```sh
+```shell
 curl --request GET --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/applications
 ```
  
@@ -97,6 +97,6 @@ Parameters:
  
 Example request:
  
-```sh
+```shell
 curl --request DELETE --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/applications/:id
 ```
--- a/doc/api/audit_events.md
+++ b/doc/api/audit_events.md
@@ -24,7 +24,7 @@ are paginated.
  
 Read more on [pagination](README.md#pagination).
  
-```bash
+```shell
 curl --header "PRIVATE-TOKEN: <your_access_token>" https://primary.example.com/api/v4/audit_events
 ```
  
@@ -91,7 +91,7 @@ Example response:
 GET /audit_events/:id
 ```
  
-```bash
+```shell
 curl --header "PRIVATE-TOKEN: <your_access_token>" https://primary.example.com/api/v4/audit_events/1
 ```
  
@@ -141,7 +141,7 @@ are paginated.
  
 Read more on [pagination](README.md#pagination).
  
-```bash
+```shell
 curl --header "PRIVATE-TOKEN: <your_access_token>" https://primary.example.com/api/v4/groups/60/audit_events
 ```
  
@@ -197,7 +197,7 @@ GET /groups/:id/audit_events/:audit_event_id
 | `id` | integer/string | yes | The ID or [URL-encoded path of the group](README.md#namespaced-path-encoding) |
 | `audit_event_id` | integer | yes | ID of the audit event |
  
-```bash
+```shell
 curl --header "PRIVATE-TOKEN: <your_access_token>" https://primary.example.com/api/v4/groups/60/audit_events/2
 ```