Skip to content

Project Management

Brian Fadely edited this page Oct 13, 2022 · 2 revisions

place holder for links to the Projects (beta) and more info on how to track projects

Draft SAR workflow using GitHub

Main branch: this primary repository branch reflects the most up-to-date publicly-accessible version of any given report year (may be a draft or final) so is a “continuum.” This is a protected branch; only Nancy would be allowed to merge in changes and publish. May also have to be private - then with copy to public, or public releases.

Development branches: developmental repository of work-in-progress for a unique SAR year (e.g. 2023, 2024). Once complete merges to the main branch. Can be multiple merges as draft stage milestones are completed, and multiple draft years simultaneously. Naming convention: “dev/YYYY” (e.g. dev/2023; dev/2024)

Feature branches: create new feature branch from dev/yyyy for working on different stocks (isolated from other stock reports - essentially what we’re doing now building the reports in Rmarkdown or Quarto). Exists only in temporary time when working/editing for draft branch. Can delete when done. Edits reviewed prior to merge back into a draft branch. Naming convention: “sarYY/stock-name” (e.g. sar23/bowhead-whale-western-arctic; sar23/harbor-seals; sar23/steller-sea-lion-western

SAR report writing/editing for each stock is using Quarto within RStudio, with output for review/comment as Google Doc or MS Word.

Releases: are zip files (not a branch), when all milestones for a release are completed. Provides for distribution to solicit comments. Can come from either main or draft branches. Public or private depending upon material.

Public comments: are received as Google Doc or MS Word track changes and comments (this is not a branch). Incorporated via stock-specific feature branch.

image