Token ends up in the url in logs

[slarse]

Probably not the best idea. It's the GitError subclasses. Example of PushFailedError log output:

[ERROR] Failed to push to https://gits-15.sys.kth.se/test-tools/c-week-1
return code: 1
stderr: To https://gits-15.sys.kth.se/test-tools/c-week-1
 ! [rejected]        master -> master (fetch first)
error: failed to push some refs to 'https://slarse:<SUPERSECRETTOKEN>@gits-15.sys.kth.se/test-tools/c-week-1'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

The SUPERSECRETTOKEN shouldn't be there (that's not the actual output)