Closed steeleb closed 3 months ago
I think I agree with the suggestion about the develop branch! I would be interested to hear if @matthewross07 has preferences
And I think we can pause on that until chl-a is officially published, but agree, getting @matthewross07 advice here would be great.
Closing after reverting a few things per PR suggestions!
Okay, here it is! Lots of words, few people will likely ever read them. I also replace the #### subheaders with bold because I don't think we have subheader depth defined anywhere and we have a guideline to use 3 or fewer levels. (This is a thing that MR mentioned offhandedly a while back, sorry if I didn't loop you in!)
Of note, I changed the
_targets.R
file to default to run theuse_stable
configuration - I know we've debugged theadmin_update
and now theuse_stable
configs, but I don't know that we've run thedefault
configuration explicitly. If I'm wrong about this, we should probably set line 31 in _targets.R todefault
for our public-facing branch.Related: while it makes sense for the 'public facing' branch to have that config set to
default
oruse_stable
, it doesn't necessarily make sense for the branch we're developing on. Maybe we create adevelop
branch after the chl-a data/pipeline gets published that we work in and release/merge with main as we publish new parameters? Tagging @mishafredmeyer and @matthewross07 here in case they have thoughts.