Built site for gh-pages

nmfs-opensci · Nov 4, 2024 · 9a8f6ff · 9a8f6ff
1 parent 928c67b
commit 9a8f6ff
Show file tree

Hide file tree

Showing 7 changed files with 13 additions and 8 deletions.
diff --git a/.nojekyll b/.nojekyll
@@ -1 +1 @@
-7b79a4a2
+24865155
diff --git a/index.html b/index.html
@@ -7,7 +7,7 @@
 <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
 
 <meta name="author" content="NMFS Open Science GitHub working group">
-<meta name="dcterms.date" content="2023-11-27">
+<meta name="dcterms.date" content="2024-11-04">
 
 <title>GitHub and Git – GitHub Guide</title>
 <style>
@@ -124,6 +124,7 @@ <h2 id="toc-title">On this page</h2>
   <li><a href="#nmfs-github-enterprise-cloud-user-agreement" id="toc-nmfs-github-enterprise-cloud-user-agreement" class="nav-link" data-scroll-target="#nmfs-github-enterprise-cloud-user-agreement"><span class="header-section-number">2.3</span> NMFS GitHub Enterprise Cloud user agreement</a></li>
   <li><a href="#request-access-to-nmfs-github-enterprise-cloud" id="toc-request-access-to-nmfs-github-enterprise-cloud" class="nav-link" data-scroll-target="#request-access-to-nmfs-github-enterprise-cloud"><span class="header-section-number">2.4</span> Request access to NMFS GitHub Enterprise Cloud</a></li>
   <li><a href="#wait-for-the-organization-invite-and-on-boarding-instructions" id="toc-wait-for-the-organization-invite-and-on-boarding-instructions" class="nav-link" data-scroll-target="#wait-for-the-organization-invite-and-on-boarding-instructions"><span class="header-section-number">2.5</span> Wait for the organization invite and on-boarding instructions</a></li>
+  <li><a href="#authenticating-to-github" id="toc-authenticating-to-github" class="nav-link" data-scroll-target="#authenticating-to-github"><span class="header-section-number">2.6</span> Authenticating to GitHub</a></li>
   </ul></li>
   <li><a href="#sec-background" id="toc-sec-background" class="nav-link" data-scroll-target="#sec-background"><span class="header-section-number">3</span> Background</a>
   <ul class="collapse">
@@ -174,7 +175,7 @@ <h2 id="toc-title">On this page</h2>
 <div class="quarto-title">
 <h1 class="title">GitHub and Git</h1>
 <p class="subtitle lead"></p><p>Guidance and Best Practices for NMFS Users<br>
-version 3.5</p><p></p>
+version 3.6</p><p></p>
 </div>
 
 
@@ -191,7 +192,7 @@ <h1 class="title">GitHub and Git</h1>
     <div>
     <div class="quarto-title-meta-heading">Published</div>
     <div class="quarto-title-meta-contents">
-      <p class="date">November 27, 2023</p>
+      <p class="date">November 4, 2024</p>
     </div>
   </div>
 
@@ -245,6 +246,10 @@ <h3 data-number="2.5" class="anchored" data-anchor-id="wait-for-the-organization
 <p>Each NMFS GitHub Enterprise organization has different on-boarding processes. This <a href="https://docs.google.com/spreadsheets/d/1WG4aEFzW2Evjp39Fq12wA4SUW-yDUZs3vYZZ0sTqiAQ/edit?usp=sharing">Google spreadsheet</a> (NOAA internal) shows you the Standard Operating Procedures (SOP) and the admins for the GitHub Enterprise organizations.</p>
 <p>Be on the look out for an invite to the GitHub Enterprise organization. Accept the invitation and then you will be able to see the <a href="https://github.com/enterprises/noaa-nmfs">NMFS GHEC organizations</a>. Once you are a member of the organization, review its SOP (in this <a href="https://docs.google.com/spreadsheets/d/1WG4aEFzW2Evjp39Fq12wA4SUW-yDUZs3vYZZ0sTqiAQ/edit?usp=sharing">Google spreadsheet</a> (NOAA internal)) for how to proceed. Reach out to your local NMFS GHEC organization admins (in the spreadsheet) if you need help.</p>
 </section>
+<section id="authenticating-to-github" class="level3" data-number="2.6">
+<h3 data-number="2.6" class="anchored" data-anchor-id="authenticating-to-github"><span class="header-section-number">2.6</span> Authenticating to GitHub</h3>
+<p>Please see the NMFS Open Science Resource Book on <a href="https://nmfs-opensci.github.io/ResourceBook/content/github/authenticating.html">installing Git and Authenticating to GitHub</a>.</p>
+</section>
 </section>
 <section id="sec-background" class="level2" data-number="3">
 <h2 data-number="3" class="anchored" data-anchor-id="sec-background"><span class="header-section-number">3</span> Background</h2>

diff --git a/index.pdf b/index.pdf
diff --git a/search.json b/search.json
@@ -18,7 +18,7 @@
     "href": "index.html#sec-quickstart",
     "title": "GitHub and Git",
     "section": "2 Quick Start",
-    "text": "2 Quick Start\nHere are the steps for getting started with GitHub at NOAA Fisheries with detailed instructions in the subsections.\n\nCreate a GitHub user account with your NOAA email.\nTurn on 2-Factor Authentication on your account.\nDownload the NMFS GitHub Enterprise Cloud user agreement and have your supervisor sign it\nRequest access to your offices’ GitHub Enterprise Cloud organization.\nWatch for an invite to the GitHub organization in your email and on-boarding instructions.\n\n\n2.1 Create a GitHub user account\nYou will need a GitHub user account that is specific to your NOAA work and that uses your NOAA email for notifications. If you have an existing GitHub account that you only use for NOAA work, you can simply add your NOAA email as the primary contact for notifications. If you have an existing GitHub account that you use for non-NOAA work, e.g. another job, university work, or personal work, then you will need to create a new GitHub account for your NOAA work.\n\nGo to www.github.com.\nCreate an account with your NOAA email. Your username should include your name, e.g. FirstLast or initialslastname. Some users add “-NOAA” to the end of their username. This is not required but helpful if you have another non-NOAA account.\nEdit your profile and add your NOAA affiliation and your real name.\n\n\n\n2.2 Turn on 2-Factor Authentication on your account\nGo to https://github.com/settings/security and turn on 2-Factor Authentication. Add multiple methods for authentication in case your primary method does not work.\nYou will not be asked to authenticate with your 2nd factor every time you log in, but you will be asked if you try to do something that might be dangerous. For example, if you are adding a collaborator to a repository, you will be asked for your 2nd factor.\n\n\n2.3 NMFS GitHub Enterprise Cloud user agreement\nDownload the GitHub Enterprise Cloud user agreement (NOAA internal) and have your supervisor sign it. You will upload this when you request access to any GitHub Enterprise organizations.\n\n\n2.4 Request access to NMFS GitHub Enterprise Cloud\nRequest access to the GitHub organization for your the office where you work and any other GitHub organization that you need access to. Use this Google form to request access. You will need to upload your user agreement.\nWait for an email inviting your to become a member of the GitHub organization. Once you accept the invitation, you see that you are listed as a member of the NMFS GHEC site. Note, you will get a 404 error unless you are a NMFS GHEC member.\n\n\n2.5 Wait for the organization invite and on-boarding instructions\nEach NMFS GitHub Enterprise organization has different on-boarding processes. This Google spreadsheet (NOAA internal) shows you the Standard Operating Procedures (SOP) and the admins for the GitHub Enterprise organizations.\nBe on the look out for an invite to the GitHub Enterprise organization. Accept the invitation and then you will be able to see the NMFS GHEC organizations. Once you are a member of the organization, review its SOP (in this Google spreadsheet (NOAA internal)) for how to proceed. Reach out to your local NMFS GHEC organization admins (in the spreadsheet) if you need help."
+    "text": "2 Quick Start\nHere are the steps for getting started with GitHub at NOAA Fisheries with detailed instructions in the subsections.\n\nCreate a GitHub user account with your NOAA email.\nTurn on 2-Factor Authentication on your account.\nDownload the NMFS GitHub Enterprise Cloud user agreement and have your supervisor sign it\nRequest access to your offices’ GitHub Enterprise Cloud organization.\nWatch for an invite to the GitHub organization in your email and on-boarding instructions.\n\n\n2.1 Create a GitHub user account\nYou will need a GitHub user account that is specific to your NOAA work and that uses your NOAA email for notifications. If you have an existing GitHub account that you only use for NOAA work, you can simply add your NOAA email as the primary contact for notifications. If you have an existing GitHub account that you use for non-NOAA work, e.g. another job, university work, or personal work, then you will need to create a new GitHub account for your NOAA work.\n\nGo to www.github.com.\nCreate an account with your NOAA email. Your username should include your name, e.g. FirstLast or initialslastname. Some users add “-NOAA” to the end of their username. This is not required but helpful if you have another non-NOAA account.\nEdit your profile and add your NOAA affiliation and your real name.\n\n\n\n2.2 Turn on 2-Factor Authentication on your account\nGo to https://github.com/settings/security and turn on 2-Factor Authentication. Add multiple methods for authentication in case your primary method does not work.\nYou will not be asked to authenticate with your 2nd factor every time you log in, but you will be asked if you try to do something that might be dangerous. For example, if you are adding a collaborator to a repository, you will be asked for your 2nd factor.\n\n\n2.3 NMFS GitHub Enterprise Cloud user agreement\nDownload the GitHub Enterprise Cloud user agreement (NOAA internal) and have your supervisor sign it. You will upload this when you request access to any GitHub Enterprise organizations.\n\n\n2.4 Request access to NMFS GitHub Enterprise Cloud\nRequest access to the GitHub organization for your the office where you work and any other GitHub organization that you need access to. Use this Google form to request access. You will need to upload your user agreement.\nWait for an email inviting your to become a member of the GitHub organization. Once you accept the invitation, you see that you are listed as a member of the NMFS GHEC site. Note, you will get a 404 error unless you are a NMFS GHEC member.\n\n\n2.5 Wait for the organization invite and on-boarding instructions\nEach NMFS GitHub Enterprise organization has different on-boarding processes. This Google spreadsheet (NOAA internal) shows you the Standard Operating Procedures (SOP) and the admins for the GitHub Enterprise organizations.\nBe on the look out for an invite to the GitHub Enterprise organization. Accept the invitation and then you will be able to see the NMFS GHEC organizations. Once you are a member of the organization, review its SOP (in this Google spreadsheet (NOAA internal)) for how to proceed. Reach out to your local NMFS GHEC organization admins (in the spreadsheet) if you need help.\n\n\n2.6 Authenticating to GitHub\nPlease see the NMFS Open Science Resource Book on installing Git and Authenticating to GitHub."
   },
   {
     "objectID": "index.html#sec-background",

diff --git a/site_libs/bootstrap/bootstrap-dark.min.css b/site_libs/bootstrap/bootstrap-dark.min.css
diff --git a/site_libs/bootstrap/bootstrap.min.css b/site_libs/bootstrap/bootstrap.min.css
diff --git a/sitemap.xml b/sitemap.xml
@@ -2,6 +2,6 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
     <loc>https://nmfs-opensci.github.io/GitHub-Guide/index.html</loc>
-    <lastmod>2024-10-01T19:27:51.743Z</lastmod>
+    <lastmod>2024-11-04T21:52:49.243Z</lastmod>
   </url>
 </urlset>