-bc command output for a GitLab repo should include /commit/ in "url"-field of JSON-file

[RetriedAgain]

If any support for GitLab is not planned/considered, you can gladly disregard this report.

RM Version: 3.0.11

When analyzing a project from GitLab + looking at a json-file of a -bc command, the "url"-fields of the individual commits have the following structure:
...<projectName>/<commitHash>

These URLs lead to 404-pages.

The structure of URLs needs to be in the form of
<projectName>/commit/<commitHash>

To test this, I created

1. a public and private repo on my own GitHub-account
2. a public and private GitLab on my own, private, GitLab-account,
3. a public and private repo on my student-account on my university's instance.

For each repo I created two commits and used the bc command in the commandline from one commit to the next.
Only through the private & public repo on my own GitHub-account was the proper URL-structure created.

[tsantalis]

@RetriedAgain
I think the fix should be easy as there is some hard-coded code for processing github URLs.

I just want from you the exact command you executed -bc .... all arguments.
Also I need to know if GitLab is using its own OAuth token, or a GitHub OAuth token works too.

I am not using GitLab. I have no idea if it works the same way as GitHub.
Our tool needs an OAuth token to access GitHub. Does GitLab have the same access policy?