Add prompts to all code blocks with bash session

developer/code/code-signing.rst

@@ -91,7 +91,7 @@ If you’re submitting a patch via GitHub (or a similar Git server), please sign
 
    .. code:: console
 
-         git config --global user.signingkey <KEYID>
+         $ git config --global user.signingkey <KEYID>
 
 
 
@@ -99,14 +99,14 @@ If you’re submitting a patch via GitHub (or a similar Git server), please sign
 
    .. code:: console
 
-         git config --global commit.gpgsign true
+         $ git config --global commit.gpgsign true
 
 
    Alternatively, manually specify when a commit is to be signed:
 
    .. code:: console
 
-         git commit -S
+         $ git commit -S
 
 
 
@@ -115,7 +115,7 @@ If you’re submitting a patch via GitHub (or a similar Git server), please sign
 
    .. code:: console
 
-         git tag -s <tag_name> -m "<tag_message>"
+         $ git tag -s <tag_name> -m "<tag_message>"
 
 
    You can also create an alias to make this easier. Edit your ``~/.gitconfig`` file. In the ``[alias]`` section, add ``stag`` to create signed tags and ``spush`` to create signed tags and push them.
@@ -171,14 +171,14 @@ In this case, you have several options to sign the commit:
 
    .. code:: console
 
-         git commit --amend -S
+         $ git commit --amend -S
 
 
    This also rewrites the commit so you need to push it forcefully:
 
    .. code:: console
 
-         git push -f
+         $ git push -f
 
 
 
@@ -186,8 +186,8 @@ In this case, you have several options to sign the commit:
 
    .. code:: console
 
-         git checkout <commit>
-         git spush
+         $ git checkout <commit>
+         $ git spush
 
 
    Now, the signature checker needs to re-check the signature. Please comment on the pull request that you would like to have the signatures checked again.