You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
\ihead{GitHub and Git SOP from NMFS Open Science (Nov 2024)}
20
+
\ihead{GitHub and Git SOP from NMFS Open Science (Jan 2025)}
21
21
documentclass: scrartcl
22
22
number-sections: true
23
23
titlepage: "plain"
@@ -301,9 +301,9 @@ Example of back-up scripts to Google Drive:
301
301
302
302
This file should provide a description of the repository. The contents of the README file will vary greatly depending on the application. Here are some tips:
303
303
304
-
***An official work product released on a NOAA-branded GitHub organization**. This is the most formal instance and the organization leaders should develop template READMEs to provide a consistent format across the products.
305
-
***A software package (e.g., R package)**. Standard components are: Badges indicating build status and version, how to install, how to use or link to documentation, where to report issues, citation.
306
-
***A report or paper.**Author, description and citation.
304
+
***An official work product released on a NOAA-branded GitHub organization**. This is the most formal case and the organization leaders should develop template READMEs to provide a consistent format across the products.
305
+
***A software or code package (e.g., R package)**. Standard components are: Badges indicating build status and version, description, how to install, how to use or link to documentation, where to report issues, authors, citation. [Example](https://github.com/nwfsc-cb/rCAX/blob/main/README.md)
306
+
***A report or paper.**Authors, description and citation.
307
307
* Add the DISCLAIMER (below) for any repository that is a 'work product'.
0 commit comments