fix broken and bot reject links (#995)

* fix broken and bot reject links * ignore more links --------- Co-authored-by: Tess Ferrandez <[email protected]>
microsoft · Sep 20, 2023 · f9d4d61 · f9d4d61
1 parent 54ea14b
commit f9d4d61
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 2 deletions.
diff --git a/docs/agile-development/advanced-topics/collaboration/why-collaboration.md b/docs/agile-development/advanced-topics/collaboration/why-collaboration.md
@@ -7,7 +7,7 @@ In engagements, we aim to be highly collaborative because when we code together,
 
 There are two common patterns we use for collaboration: Pairing and swarming.
 
-**Pair programming** (“pairing”) - two software engineers assigned to, and working on, one shared story at a time during the sprint. The Dev Lead assigns a user story to two engineers -- one primary engineer (story owner) and one secondary engineer (pairing assignee). The definition aligns with the Agile Alliance’s [definition](https://www.agilealliance.org/glossary/pairing).
+**Pair programming** (“pairing”) - two software engineers assigned to, and working on, one shared story at a time during the sprint. The Dev Lead assigns a user story to two engineers -- one primary engineer (story owner) and one secondary engineer (pairing assignee).
 
 **Swarm programming** (“swarming”) - three or more software engineers collaborating on a high-priority item to bring it to completion.
 

diff --git a/linkcheck.json b/linkcheck.json
@@ -45,7 +45,13 @@
       "https://blog.prototypr.io/software-documentation-types-and-best-practices-1726ca595c7f",
       "https://towardsdatascience.com/",
       "https://medium.com/",
-      "https://github.com/"
+      "https://github.com/",
+      "https://docs.github.com/",
+      "https://behave.readthedocs.io/",
+      "https://blog.insightdatascience.com",
+      "https://www.w3.org/",
+      "https://mtirion.medium.com/",
+      "https://chrieke.medium.com/"
     ],
     "only_errors": true
   }