Update redirecting links in documentation

Even though these links were still reaching the intended page, it is best not to rely on redirects.

Author: per1234

docs/CONTRIBUTING.md

@@ -12,17 +12,17 @@ There are several ways you can get involved:
 | - Bug fix<br/>- Enhancement                       | Pull Request (read the [pull request guidelines][prs])  |
 | Monetary                                          | - [Donate][donate]<br/>- [Buy official products][store] |
 
-[forum]: https://forum.arduino.cc/index.php?board=3.0
+[forum]: https://forum.arduino.cc/c/using-arduino/project-guidance/19
 [issues]: #issue-reports
 [nightly]: installation.md#nightly-builds
 [prs]: #pull-requests
-[donate]: https://www.arduino.cc/en/Main/Contribute
+[donate]: https://www.arduino.cc/en/donate/
 [store]: https://store.arduino.cc
 
 ## Issue Reports
 
 Do you need help or have a question about using Arduino Lint? Support requests should be made to the
-[Arduino forum](https://forum.arduino.cc/index.php?board=3.0).
+[Arduino forum](https://forum.arduino.cc/c/using-arduino/project-guidance/19).
 
 High quality bug reports and feature requests are valuable contributions to the Arduino Lint project.
 
@@ -31,8 +31,8 @@ High quality bug reports and feature requests are valuable contributions to the
 - Give the [nightly build](installation.md#nightly-builds) a test drive to see if your issue was already resolved.
 - Search [existing pull requests and issues](https://github.com/arduino/arduino-lint/issues?q=) to see if it was already
   reported. If you have additional information to provide about an existing issue, please comment there. You can use
-  [GitHub's "Reactions" feature](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments) if you
-  only want to express support.
+  [GitHub's "Reactions" feature](https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) if
+  you only want to express support.
 
 ### Qualities of an excellent report
 
@@ -55,16 +55,16 @@ submitting a PR:
 
 - Create small PRs that are narrowly focused on addressing a single concern.
 - Write tests for the code you wrote.
-- Maintain [**clean commit history**](http://www.freshconsulting.com/atomic-commits) and use
-  [**meaningful commit messages**](http://chris.beams.io/posts/git-commit). PRs with messy commit history are difficult
-  to review and require a lot of work to be merged.
+- Maintain [**clean commit history**](https://www.freshconsulting.com/insights/blog/atomic-commits/) and use
+  [**meaningful commit messages**](https://cbea.ms/git-commit/). PRs with messy commit history are difficult to review
+  and require a lot of work to be merged.
 - <a id="breaking"></a> If the PR contains a breaking change, please start the commit message and PR title with the
   string **[breaking]**. Don't forget to describe in the PR description what changes users might need to make in their
   workflow or application due to this PR. A breaking change is a change that forces users to change their command-line
   invocations or parsing of the JSON formatted output when upgrading from an older version of Arduino Lint.
 - PR titles indirectly become part of the CHANGELOG so it's crucial to provide a good record of **what** change is being
   made in the title; **why** it was made will go in the PR description, along with
-  [a link to a GitHub issue](https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)
+  [a link to a GitHub issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
   if one exists.
 - Open your PR against the `main` branch.
 - Your PR must pass all [CI](https://en.wikipedia.org/wiki/Continuous_integration) tests before we will merge it. You

docs/index.md

@@ -41,7 +41,7 @@ accepted by this flag are:
 [Arduino Library Manager](https://docs.arduino.cc/software/ide-v1/tutorials/installing-libraries#using-the-library-manager)
 is the best way to provide installation and updates of Arduino libraries. In order to be accepted for inclusion in
 Library Manager, a library is required to meet
-[some requirements](https://github.com/arduino/Arduino/wiki/Library-Manager-FAQ).
+[some requirements](https://github.com/arduino/library-registry/blob/main/FAQ.md#readme).
 
 **Arduino Lint** provides checks for these requirements as well, controlled by the `--library-manager` flag.
 
@@ -79,8 +79,7 @@ Additional configuration options intended for internal use or development can be
 [continuous integration](https://en.wikipedia.org/wiki/Continuous_integration) system. Running the tool after each
 change to the project can allow you to identify any problems that were introduced.
 
-This is easily done by using the `arduino/arduino-lint-action`
-[GitHub Actions](https://docs.github.com/en/free-pro-team@latest/actions) action:
+This is easily done by using the `arduino/arduino-lint-action` [GitHub Actions](https://docs.github.com/actions) action:
 https://github.com/arduino/arduino-lint-action
 
 Add [a simple workflow file](https://github.com/arduino/arduino-lint-action#usage) to the repository of your Arduino
@@ -89,7 +88,7 @@ project and GitHub will automatically run Arduino Lint on every pull request and
 ## Support and feedback
 
 You can discuss or get assistance with using **Arduino Lint** on the
-[Arduino Forum](https://forum.arduino.cc/index.php?board=3.0).
+[Arduino Forum](https://forum.arduino.cc/c/using-arduino/project-guidance/19).
 
 Feedback is welcome! Please submit feature requests or bug reports to the
 [issue tracker](CONTRIBUTING.md#issue-reports).

internal/rule/ruleconfiguration/ruleconfiguration.go

@@ -1258,7 +1258,7 @@ var configurations = []Type{
 		Brief:            "no readme",
 		Description:      "None of the standard README file names (e.g., `README.md`) were found in the library's root folder. This file provides interested parties with a convenient and standardized location to get information about the project.",
 		MessageTemplate:  "No readme found. Please document your library.",
-		Reference:        "https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes",
+		Reference:        "https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes",
 		DisableModes:     nil,
 		EnableModes:      []rulemode.Type{rulemode.Default},
 		InfoModes:        nil,
@@ -1275,7 +1275,7 @@ var configurations = []Type{
 		Brief:            "no license file",
 		Description:      "None of the standard license file names (e.g., `LICENSE.txt`) were found in the library's root folder. This file provides interested parties with a convenient and standardized location to get information about the project's licensing and is also used by GitHub for automatic license type classification.",
 		MessageTemplate:  "No license file found.",
-		Reference:        "https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/licensing-a-repository",
+		Reference:        "https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository",
 		DisableModes:     nil,
 		EnableModes:      []rulemode.Type{rulemode.Default},
 		InfoModes:        nil,
@@ -1462,7 +1462,7 @@ var configurations = []Type{
 		Brief:            "no readme",
 		Description:      "None of the standard README file names (e.g., `README.md`) were found in the sketch folder. This file provides interested parties with a convenient and standardized location to get information about the project.",
 		MessageTemplate:  "No readme found. Please document your sketch.",
-		Reference:        "https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes",
+		Reference:        "https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes",
 		DisableModes:     nil,
 		EnableModes:      []rulemode.Type{rulemode.Default},
 		InfoModes:        nil,
@@ -1479,7 +1479,7 @@ var configurations = []Type{
 		Brief:            "no license file",
 		Description:      "None of the standard license file names (e.g., `LICENSE.txt`) were found in the sketch's root folder. This file provides interested parties with a convenient and standardized location to get information about the project's licensing and is also used by GitHub for automatic license type classification.",
 		MessageTemplate:  "No license file found.",
-		Reference:        "https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/licensing-a-repository",
+		Reference:        "https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository",
 		DisableModes:     nil,
 		EnableModes:      []rulemode.Type{rulemode.Default},
 		InfoModes:        nil,
@@ -1530,7 +1530,7 @@ var configurations = []Type{
 		Brief:            "no readme",
 		Description:      "None of the standard README file names (e.g., `README.md`) were found in the platform folder. This file provides interested parties with a convenient and standardized location to get information about the project.",
 		MessageTemplate:  "No readme found. Please document your boards platform.",
-		Reference:        "https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes",
+		Reference:        "https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes",
 		DisableModes:     []rulemode.Type{rulemode.Default},
 		EnableModes:      nil,
 		InfoModes:        nil,
@@ -1547,7 +1547,7 @@ var configurations = []Type{
 		Brief:            "no license file",
 		Description:      "None of the standard license file names (e.g., `LICENSE.txt`) were found in the platform folder. This file provides interested parties with a convenient and standardized location to get information about the project's licensing and is also used by GitHub for automatic license type classification.",
 		MessageTemplate:  "No license file found.",
-		Reference:        "https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/licensing-a-repository",
+		Reference:        "https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository",
 		DisableModes:     []rulemode.Type{rulemode.Default},
 		EnableModes:      nil,
 		InfoModes:        nil,