Use GitHub's official github.com domain and drop github.com domain

[HonkingGoose]

Describe the proposed change(s).

Todos

• Replace github.com with github.com in our code.

Context

Our custom github.com domain sometimes gets blocked by GitHub's Umbrella protection system. We then need to contact GitHub to get unblocked.

To get around the "we get blocked by GitHub problem" we wanted to transfer control of the custom domain to GitHub. But that went nowhere:

• Transfer Renovate's github.com redirect domain to GitHub #29370

In the issue above, a user suggested we use github.com instead, and @rarkins agreed.

[HonkingGoose]

Questions for @rarkins:

1. How to confirm the new domain works as expected? Worst case scenario: we deploy the change, it does not work as we expect, and we ping everybody... 😱

2. Short term: Mend should keep control of the old custom domain for a while, so we can revert to the old state if needed.

3. Long term: should Mend keep controlling the old domain? Say someone with bad plans buys the old domain, and somehow messes things up for Renovate users?

4. Do we need to write code to check if Renovate config files mention the old domain github.com? I'm thinking of users that somehow hard-coded Renovate to use that domain, which could become a risk when Mend drops the domain?

[RahulGautamSingh]

Regarding point 4.

We use the links with users in 2 cases:

1. Comments/ PR body: Can be tested using github ui

2. Commit message/body: Can be tested by making a git commit

No need to write code IMO, except test runs on the PR which introduces this change.

[renovate-release]

🎉 This issue has been resolved in version 38.57.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 38.57.1

Your semantic-release bot 📦🚀