Workflow: automated link checker for markdown with link updates in docs (#83)

* Repair/remove broken links

* Link updates to markdown format

* Link updates to markdown format

* Exclude forum.unity.com (Too many redirects)

* Exclude forum.Unity.com

* Change --exclude argument

* Update CheckMarkdownLinks.yml

* Update CheckMarkdownLinks.yml

* Update CheckMarkdownLinks.yml

* Update CheckMarkdownLinks.yml

* Add Unity License

* Change CI badge to point at fork: Mathijs-Bakker/Extenject

Author: Mathijs-Bakker

.github/workflows/CheckMarkdownLinks.yml

@@ -10,7 +10,7 @@ jobs:
       id: lc
       uses: peter-evans/link-checker@v1
       with:
-        args: -v -r *
+        args: -v --exclude "https://forum.unity.com" --recursive *
     - name: Create Issue From File
       uses: peter-evans/create-issue-from-file@v2
       with:

.github/workflows/main.yml

@@ -11,7 +11,7 @@ jobs:
   #enable this job to request a manual unity license
   Request-License:
     runs-on: ubuntu-latest
-    if: true
+    if: false
     steps:
       - name: Checkout repository
         uses: actions/checkout@v2

Documentation/WritingAutomatedTests.md

@@ -297,7 +297,7 @@ public class SpaceShipTests : ZenjectIntegrationTestFixture
 
 After `PostInstall()` is called, our integration test is injected, so we can define `[Inject]` fields on it like above if we don't want to call `Container.Resolve` for every test.
 
-Note that we can yield our coroutine to test behaviour across time.  If you are unfamiliar with how Unity's test runner works (and in particular how 'playmode test' work) please see the [unity documentation]()https://docs.unity3d.com/Manual/testing-editortestsrunner.html.
+Note that we can yield our coroutine to test behaviour across time.  If you are unfamiliar with how Unity's test runner works (and in particular how 'playmode test' work) please see the [unity documentation](https://docs.unity3d.com/Packages/[email protected]/manual/index.html).
 
 Every zenject integration test is broken up into three phases: