Branching Structure

Raw Data Branch

xxxx-xxxx-data (e.g. fcre-catwalk-data)

Content

Raw Sensor Data (e.g. fcre-waterquality.csv)

Note: The data are directly pushed from the gateways and should not be altered by anyone rather than the gateways.

Workflow Files (e.g. fcre-catwalk-qaqc.yml)

Note: For workflow trigger on push on a specific branch, the workflow file should be in that branch. But, for manual workflow run (i.e. workflow_dispatch), the workflow file should be present in the default branch (i.e. master or main). If we need both of these triggers, we must have two copies of the same workflow file. To avoid confusion, we recommend not enabling manual workflow run and having just one copy of the workflow file in the raw data branch.

QAQC Data Branch

xxxx-xxxx-data-qaqc (e.g. fcre-catwalk-data-qaqc)

Content

QAQC R Scripts (e.g. R/QAQC_workflow.R)

Maintenance Logs (e.g. CAT_MaintenanceLog.txt)

QAQC Data (e.g. fcre-waterquality-L1.csv)

Legacy Sensor Data Files

Note: Legacy sensor data files are manually split from the original sensor data files (usually once a year) to avoid exceeding the 100 MB GitHub file size limit.