Update docs.github.com links

.github/CONTRIBUTING.md

@@ -44,7 +44,7 @@ In case you've encountered a bug, please make sure:
 
 Pull requests are welcome! If you never created a pull request before, here are some tutorials:
 
-- [Creating a pull request](https://help.github.com/articles/creating-a-pull-request/)
+- [Creating a pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)
 - [How to Contribute to an Open Source Project on GitHub](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github)
 
 Please keep the following in mind:
@@ -57,7 +57,8 @@ Please keep the following in mind:
 
 Unsure about whether you should open a pull request? Feel free to discuss it first in a ticket.
 
-[Fork](https://help.github.com/articles/fork-a-repo/) the repository to get started, and set it up on your machine:
+[Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) the repository to get started, and set it up on
+your machine:
 
 ```bash
 git clone https://github.com/<your-github-username>/release-it

README.md

@@ -156,7 +156,8 @@ remote.
 ## GitHub Releases
 
 GitHub projects can have releases attached to Git tags, containing release notes and assets. There are two ways to add
-[GitHub releases](https://help.github.com/articles/creating-releases) in your release-it flow:
+[GitHub releases](https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases) in your
+release-it flow:
 
 1. Automated (requires a `GITHUB_TOKEN`)
 2. Manual (using the GitHub web interface with pre-populated fields)

docs/git.md

@@ -23,8 +23,9 @@ release-it should be able to do the same.
 
 The following help pages might be useful:
 
-- [Connecting to GitHub with SSH](https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh)
-- [Managing remote repositories](https://docs.github.com/en/github/using-git/managing-remote-repositories) (GitHub)
+- [Connecting to GitHub with SSH](https://docs.github.com/en/authentication/connecting-to-github-with-ssh)
+- [Managing remote repositories](https://docs.github.com/en/get-started/getting-started-with-git/managing-remote-repositories)
+  (GitHub)
 - [Configure SSH and two-step verification](https://support.atlassian.com/bitbucket-cloud/docs/configure-ssh-and-two-step-verification/)
   (Bitbucket)
 - [GitLab and SSH keys](https://gitlab.com/help/ssh/README.md)

docs/github-releases.md

@@ -10,8 +10,8 @@ Unsurprisingly, release-it uses this feature extensively
 
 See the screenshot on the right for an overview of what release-it automates.
 
-To add [GitHub releases](https://help.github.com/articles/creating-releases/) in your release-it flow, there are two
-options:
+To add [GitHub releases](https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases) in your
+release-it flow, there are two options:
 
 1. Automated. This requires a personal access token.
 2. Manual. The GitHub web interface will be opened with pre-populated fields.