Thanks, I didn't know about console.

I'll use it in my Markdowns so that I'll be ready when GitHub implements this feature.

Users can also solve this problem themselves via their own config. For example, Zsh users can create a dirt simple pass-thru dollar function like so:

# .zshrc
function \$ { "$@"; }

Bash users can't make a function called $, but if they are using ble.sh they can modify the command before it executes:

# .bashrc
ble/function#advice around ble/widget/default/accept-line '
  if [[ "${_ble_edit_str:0:2}" == "$ " ]]; then
    ble/widget/beginning-of-logical-line
    ble/widget/insert-string "${_ble_edit_str:2}"
    ble/widget/kill-forward-logical-line
  fi
  ble/function#advice/do
'

And in Fish, you can add your own paste scrubber:

function fish_paste_scrubber
    # run the Fish default
    fish_clipboard_paste
    # remove any leading dollar signs from the pasted command
    commandline -r (string replace -r '^\$ ' '' (commandline))
end

Then you have to bind it to your paste key sequence in fish_user_key_bindings:

function fish_user_key_bindings
    bind \cv fish_paste_scrubber
    # ... other keybindings ...
end

It'd still be a good idea to implement this feature. Just thought it worth mentioning this can be solved on the user end too. Since things like GitLab and BitBucket and blogs and articles etc exist, users will forever be annoyed by this problem if they don't apply a fix themselves.