Deploying to gh-pages from @ 567000a 🚀

_preview/203/_sources/reference/membership.md

@@ -70,6 +70,6 @@ is removed from the `leap-pangeo-users` group.
 
 ![](../images/member_sign_up_schematic.png)
 
-All data relevant to LEAP membership is centrally processed in a spreadsheet with access limited to LEAP staff. To allow LEAP members access to the JupyterHub (and the associated storage and compute resources; all managed by 2i2c) the [](support.data_compute_team) maintains a set of Github Actions that parse the relevant data like github usernames and membership expiration, and add users to the appropriate [teams](reference.membership.team-resources).
+All data relevant to LEAP membership is centrally processed in a spreadsheet with access limited to LEAP staff. To allow LEAP members access to the JupyterHub (and the associated storage and compute resources; all managed by 2i2c) the [](support.data_compute_team) maintains a set of [Github Actions](https://github.com/leap-stc/member_management/actions/workflows/read_sheet.yaml)(the member management repository is private) that parse the relevant data like github usernames and membership expiration, and add users to the appropriate [teams](reference.membership.team-resources).
 For normal operations users should [apply](users.membership.apply) and wait a few days until they are approved, entered, and signed up for access.
 For urgent situations (like events, classes) that require expedited sign up please refer to [](guide.team.admin.member_signup_troubleshooting).

_preview/203/reference/membership.html

@@ -517,7 +517,7 @@ <h2>Offboarding Process<a class="headerlink" href="#offboarding-process" title="
 <div class="section" id="member-sign-up-procedure">
 <span id="reference-member-sign-up"></span><h2>Member Sign Up Procedure<a class="headerlink" href="#member-sign-up-procedure" title="Permalink to this headline">¶</a></h2>
 <p><img alt="" src="../_images/member_sign_up_schematic.png" /></p>
-<p>All data relevant to LEAP membership is centrally processed in a spreadsheet with access limited to LEAP staff. To allow LEAP members access to the JupyterHub (and the associated storage and compute resources; all managed by 2i2c) the <a class="reference internal" href="../support.html#support-data-compute-team"><span class="std std-ref">Data and Computation Team</span></a> maintains a set of Github Actions that parse the relevant data like github usernames and membership expiration, and add users to the appropriate <a class="reference internal" href="#reference-membership-team-resources"><span class="std std-ref">teams</span></a>.
+<p>All data relevant to LEAP membership is centrally processed in a spreadsheet with access limited to LEAP staff. To allow LEAP members access to the JupyterHub (and the associated storage and compute resources; all managed by 2i2c) the <a class="reference internal" href="../support.html#support-data-compute-team"><span class="std std-ref">Data and Computation Team</span></a> maintains a set of <a class="reference external" href="https://github.com/leap-stc/member_management/actions/workflows/read_sheet.yaml">Github Actions</a>(the member management repository is private) that parse the relevant data like github usernames and membership expiration, and add users to the appropriate <a class="reference internal" href="#reference-membership-team-resources"><span class="std std-ref">teams</span></a>.
 For normal operations users should <a class="reference internal" href="#users-membership-apply"><span class="std std-ref">apply</span></a> and wait a few days until they are approved, entered, and signed up for access.
 For urgent situations (like events, classes) that require expedited sign up please refer to <a class="reference internal" href="../guides/team_guide.html#guide-team-admin-member-signup-troubleshooting"><span class="std std-ref">Member Sign Up Troubleshooting</span></a>.</p>
 </div>