fix links, check circleci artifacts

_posts/2020-03-12-Steering-Group-executive-summary,-action-items,-and-minutes.md

@@ -21,9 +21,13 @@ We will be using the resulting list of communication channels to share the relea
 We discussed generating an example slide deck that community members can  use (or pick from) when they want to present BIDS.
 
 We discussed considerations for when to open a repository under the BIDS standard organization on GitHub.
-Previously, community members have opened repositories under the BIDS [GitHub organization](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-organizations){:target="_blank"} named [`bids-standard`](https://github.com/bids-standard){:target="_blank"}.
+Previously, community members have opened repositories under the BIDS
+[GitHub organization](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/about-organizations){:target="_blank"}
+named [`bids-standard`](https://github.com/bids-standard){:target="_blank"}.
 We want to codify guidelines to govern this.
-The plan is that there should be multiple people committed to the repository (otherwise it is better under the personal GitHub account), the maintainers should be clearly identifiable (e.g., as a [CODEOWNERS file](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners#about-code-owners){:target="_blank"} at the top level), there should be a code of conduct in the repository that is consistent with that of the BIDS specification, and (as a consequence of the code of conduct) the repository should welcome contributions from others.
+The plan is that there should be multiple people committed to the repository (otherwise it is better under the personal GitHub account), the maintainers should be clearly identifiable (e.g., as a
+[CODEOWNERS file](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#about-code-owners){:target="_blank"}
+at the top level), there should be a code of conduct in the repository that is consistent with that of the BIDS specification, and (as a consequence of the code of conduct) the repository should welcome contributions from others.
 
 We want to host another [Community Forum](https://bids.neuroimaging.io/2020/01/02/announcement-community-forum-events.html){:target="_blank"} (but not too frequent) and potentially a starter kit/demo in the Open Science Room at [OHBM](https://www.humanbrainmapping.org){:target="_blank"}.
 

_posts/2020-11-02-BIDS-ASL-community-review.md

@@ -10,7 +10,7 @@ The BIDS community is preparing to merge the ASL (Arterial Spin Labeling) extens
 
 <!--more-->
 
-The BIDS community is preparing to merge the ASL (Arterial Spin Labeling) extension. The [updated draft](https://bids-specification--652.org.readthedocs.build/en/652/04-modality-specific-files/01-magnetic-resonance-imaging-data.html#arterial-spin-labeling-perfusion-data){:target="_blank"} is available for review, and comments and suggestions may be submitted on [GitHub](https://github.com/bids-standard/bids-specification/pull/652){:target="_blank"}. The community review will close on Friday (Nov 13th) at 11:59pm PT (pacific time)
+The BIDS community is preparing to merge the ASL (Arterial Spin Labeling) extension. The updated draft is available for review, and comments and suggestions may be submitted on [GitHub](https://github.com/bids-standard/bids-specification/pull/652){:target="_blank"}. The community review will close on Friday (Nov 13th) at 11:59pm PT (pacific time)
 
 This BIDS extension seeks to establish how ASL data and additional metadata are organized within the BIDS structure. This encompasses the ASL sequences provided in the consensus paper (Alsop 2014), including single- and multi-time point pulsed and (pseudo)-continuous ASL.
 

_posts/2021-11-08-BIDS-Microscopy-community-review.md

@@ -10,8 +10,12 @@ The BIDS community is preparing to merge the Microscopy extension and are openin
 
 <!--more-->
 
-The updated draft is available for review at: [https://bids-specification--881.org.readthedocs.build/en/881/04-modality-specific-files/10-microscopy.html](https://bids-specification--881.org.readthedocs.build/en/881/04-modality-specific-files/10-microscopy.html){:target="_blank"}, and comments and suggestions may be submitted on GitHub at: [https://github.com/bids-standard/bids-specification/pull/881](https://github.com/bids-standard/bids-specification/pull/881){:target="_blank"}. The community review will close on Friday, November 19 at 11:59pm PT (pacific time)
+The updated draft is available for review and comments and suggestions may be submitted on GitHub at:
+[https://github.com/bids-standard/bids-specification/pull/881](https://github.com/bids-standard/bids-specification/pull/881){:target="_blank"}.
+The community review will close on Friday, November 19 at 11:59pm PT (pacific time)
 
-This BIDS extension proposal seeks to establish how microscopy data and associated metadata are organized within the BIDS structure. It covers more than [15 different types of microscopy modalities](https://bids-specification--881.org.readthedocs.build/en/881/04-modality-specific-files/10-microscopy.html#modality-suffixes){:target="_blank"} (bright-field microscopy, electron microscopy, confocal, ...) and can be used to structure non-brain data. This BEP team has already integrated the `sample` entity, the `sample.tsv` file, and incorporated animal metadata into the `participants.tsv`. 
+This BIDS extension proposal seeks to establish how microscopy data and associated metadata are organized within the BIDS structure.
+It covers more than 15 different types of microscopy modalities (bright-field microscopy, electron microscopy, confocal, ...) and can be used to structure non-brain data.
+This BEP team has already integrated the `sample` entity, the `sample.tsv` file, and incorporated animal metadata into the `participants.tsv`.
 
-The final review entails a two-week period for public commenting, with a possibility of extension for unresolved discussion. Once public comments are concluded, there will be a one-week freeze, during which only critical issues will be considered. (For more details on the release protocol, see [https://github.com/bids-standard/bids-specification/blob/master/Release_Protocol.md](https://github.com/bids-standard/bids-specification/blob/master/Release_Protocol.md){:target="_blank"}) 
+The final review entails a two-week period for public commenting, with a possibility of extension for unresolved discussion. Once public comments are concluded, there will be a one-week freeze, during which only critical issues will be considered. (For more details on the release protocol, see [https://github.com/bids-standard/bids-specification/blob/master/Release_Protocol.md](https://github.com/bids-standard/bids-specification/blob/master/Release_Protocol.md){:target="_blank"})

md_link_check_config.json

@@ -3,6 +3,12 @@
       {
         "pattern": "^https://github.com"
       },
+      {
+        "pattern": "^https://docs.github.com/.*"
+      },
+      {
+        "pattern": "^https://guides.github.com/.*"
+      },
       {
         "pattern": "^./"
       },