cis-processing is meant to be a very general workflow that strings together Singularity images that need to be more strongly versioned. That said, we have had breaking changes in the past, so we should start versioning this repo. Since we don't have individual images associated with versions of this workflow, I propose that we start versioning with branches and separate folders on the HPC.
We make a branch for a given version when we are certain it's stable (e.g., 0.0.1). Then we clone that branch to the HPC, resulting in a set of folders like this:
This will mean removing the folder /home/data/cis/cis-processing, which is currently set up as the actual repo instead of as a general folder containing repo subfolders.
cis-processing is meant to be a very general workflow that strings together Singularity images that need to be more strongly versioned. That said, we have had breaking changes in the past, so we should start versioning this repo. Since we don't have individual images associated with versions of this workflow, I propose that we start versioning with branches and separate folders on the HPC.
We make a branch for a given version when we are certain it's stable (e.g.,
0.0.1
). Then we clone that branch to the HPC, resulting in a set of folders like this:/home/data/cis/cis-processing/latest
(master)/home/data/cis/cis-processing/v0.0.1
(branch 0.0.1)This will mean removing the folder
/home/data/cis/cis-processing
, which is currently set up as the actual repo instead of as a general folder containing repo subfolders.