fix: broken urls to avoid markdown link check failures

.github/markdown-link-check-config.json

@@ -0,0 +1,6 @@
+{
+  "retryOn429": true,
+  "retryCount": 2,
+  "fallbackRetryDelay": "5s",
+  "aliveStatusCodes": [200, 206, 429]
+}

.github/workflows/link_and_spell_check.yml

@@ -34,6 +34,7 @@ jobs:
       # cspell:words gaurav
       uses: gaurav-nelson/github-action-markdown-link-check@v1
       with:
+        config-file: '.github/markdown-link-check-config.json'
         use-verbose-mode: 'yes'
       if: ${{ success() || failure() }}
     - name: "Check spelling in changed files"

minutes/sc-meeting-2022-08.md

@@ -1,8 +1,8 @@
 # Steering Committee Meeting August 2022
 
 Attendance: Alex Chernoguzov, Alex McCaskey, Bettina Heim, Kalan Snyder,
 Laurent Ajdnik (Guest), Ross Duncan, Sonia Pignorel, Tom Lubinski,
 Vicente Leyton-Ortega
 
 ## Meeting agenda
 
@@ -69,6 +69,6 @@
 good platform for IR inspection; Nvidia will bring tooling and a new community
 to QIR.
 - References
-  - [Base Profile Specification](https://github.com/qir-alliance/qir-spec/blob/main/specification/under_development/profiles/Base_Profile.md)
+  - [Base Profile Specification](https://github.com/qir-alliance/qir-spec/blob/1.0/specification/profiles/Base_Profile.md)
   - [Runtime Initialization Workstream](https://github.com/amccaskey/.github/blob/main/workstreams/Runtime_Init_Finalize_EntryPoint_Workstream.md)
   - [QIR Alliance Project Charter](https://github.com/qir-alliance/.github/blob/main/Project_Organization.md)

workflow-templates/link_and_spell_check.yml

@@ -34,6 +34,7 @@ jobs:
       # cspell:words gaurav
       uses: gaurav-nelson/github-action-markdown-link-check@v1
       with:
+        config-file: 'utils/markdown-link-check-config.json'
         use-verbose-mode: 'yes'
       if: ${{ success() || failure() }}
     - name: "Check spelling in changed files"

workflow-templates/utils/markdown-link-check-config.json

@@ -0,0 +1,6 @@
+{
+  "retryOn429": true,
+  "retryCount": 2,
+  "fallbackRetryDelay": "5s",
+  "aliveStatusCodes": [200, 206, 429]
+}

workflow-templates/utils/md_lint_config.yml

@@ -1,6 +1,6 @@
 # For more info on markdown lint configurations, see also
 # https://github.com/DavidAnson/markdownlint/blob/main/schema/.markdownlint.yaml
-# https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md
+# https://github.com/markdownlint/markdownlint/blob/main/docs/RULES.md
 
 default: true
 line-length:

workstreams/Adaptive_Profile_Workstream.md

@@ -60,7 +60,7 @@ computations with certain data types and non-trivial control flow structures. It
 will limit expressiveness to guarantee that the program always terminates (no
 unbounded loops or recursions). This specification will replace what is
 currently drafted as [Profile
-B](https://github.com/qir-alliance/qir-spec/blob/main/specification/v0.1/7_Profiles.md#profile-a-basic-quantum-functionality)
+B](https://github.com/qir-alliance/qir-spec/blob/1.0/specification/legacy/7_Profiles.md#profile-a-basic-quantum-functionality)
 on the [specification repository](https://github.com/qir-alliance/qir-spec).
 
 Like the Base Profile, the Adaptive Profile should not rely on any particular
@@ -70,7 +70,7 @@ instruction set. The profile and the quantum instruction set (QIS) selection
 together determine how the program IR should be represented.
 
 A similar specification for the Base Profile can be found
-[here](https://github.com/qir-alliance/qir-spec/blob/main/specification/under_development/profiles/Base_Profile.md).
+[here](https://github.com/qir-alliance/qir-spec/blob/1.0/specification/profiles/Base_Profile.md).
 The specification of the Adaptive Profile should follow a similar outline for
 the sake of consistency and comprehensiveness of the specification.
 
@@ -82,13 +82,13 @@ the Adaptive Profile:
 - Composite data types: <br/>
   The use of composite data types such as [structure
   types](https://llvm.org/doxygen/group__LLVMCCoreTypeStruct.html) including
-  [tuples](https://github.com/qir-alliance/qir-spec/blob/main/specification/v0.1/1_Data_Types.md#tuples-and-user-defined-types),
+  [tuples](https://github.com/qir-alliance/qir-spec/blob/1.0/specification/legacy/1_Data_Types.md#tuples-and-user-defined-types),
   and [sequential
   types](https://llvm.org/doxygen/group__LLVMCCoreTypeSequential.html) including
-  [arrays](https://github.com/qir-alliance/qir-spec/blob/main/specification/v0.1/1_Data_Types.md#arrays)
+  [arrays](https://github.com/qir-alliance/qir-spec/blob/1.0/specification/legacy/1_Data_Types.md#arrays)
   is not supported within an Adaptive Profile. This also precludes the use of
   such data structures for [callable
-  values](https://github.com/qir-alliance/qir-spec/blob/main/specification/v0.1/2_Callables.md);
+  values](https://github.com/qir-alliance/qir-spec/blob/1.0/specification/legacy/2_Callables.md);
   i.e., the usage of subroutines as first class values is not supported within
   the Adaptive Profile, and the use of [function
   types](https://llvm.org/doxygen/group__LLVMCCoreTypeFunction.html) is limited

workstreams/Base_Profile_Workstream.md

@@ -49,7 +49,7 @@ the requirements outlined [above](#requirements). The intent is for the Base
 Profile to permit expressing quantum programs that contain no control flow or
 classical computations during execution. This specification will replace what is
 currently drafted as [Profile
-A](https://github.com/qir-alliance/qir-spec/blob/main/specification/v0.1/7_Profiles.md#profile-a-basic-quantum-functionality)
+A](https://github.com/qir-alliance/qir-spec/blob/1.0/specification/legacy/7_Profiles.md#profile-a-basic-quantum-functionality)
 on the [specification repository](https://github.com/qir-alliance/qir-spec).
 
 In addition to the Base Profile itself, one or more quantum instruction set(s)
@@ -67,7 +67,7 @@ specification that contains guidance for defining and documenting addition
 quantum instruction sets going forward.
 
 A template for a specification definition can be found
-[here](https://github.com/CommunitySpecification/1.0/blob/master/7._CS_Template.md).
+[here](https://github.com/CommunitySpecification/1.0/blob/main/7._CS_Template.md).
 This may serve as inspiration but it is not required to follow the template
 precisely.
 
@@ -96,13 +96,13 @@ Profile:
 - Composite data types: <br/>
   The use of composite data types such as [structure
   types](https://llvm.org/doxygen/group__LLVMCCoreTypeStruct.html) including
-  [tuples](https://github.com/qir-alliance/qir-spec/blob/main/specification/v0.1/1_Data_Types.md#tuples-and-user-defined-types),
+  [tuples](https://github.com/qir-alliance/qir-spec/blob/1.0/specification/legacy/1_Data_Types.md#tuples-and-user-defined-types),
   and [sequential
   types](https://llvm.org/doxygen/group__LLVMCCoreTypeSequential.html) including
-  [arrays](https://github.com/qir-alliance/qir-spec/blob/main/specification/v0.1/1_Data_Types.md#arrays)
+  [arrays](https://github.com/qir-alliance/qir-spec/blob/1.0/specification/legacy/1_Data_Types.md#arrays)
   is not supported within a Base Profile compliant program. This also precludes
   the use of such data structures for [callable
-  values](https://github.com/qir-alliance/qir-spec/blob/main/specification/v0.1/2_Callables.md);
+  values](https://github.com/qir-alliance/qir-spec/blob/1.0/specification/legacy/2_Callables.md);
   i.e., the usage of subroutines as first class values is not supported within
   the Base Profile, and the use of [function
   types](https://llvm.org/doxygen/group__LLVMCCoreTypeFunction.html) is limited