[ ] I've updated AUTHORS.md with my name (if I want to)
Description
This project is released in two scenarios:
Automatically for the weekly data refresh, where we get the latest items
Manually, when development has new stuff to deliver to users
Both of these things take (took) place on master branch. But, this was problematic because these two scenarios differ in lifecycle. One runs automatically, the other, manually. Specifically, development work on master would get whisked away: conflated into the weekly data refresh, no matter if it was really intended to be released.
One solution to this is this to have a separate release branch. That way, the weekly data refresh can be applied to it, and not to master. Then, master can work on what it needs to without worry of any timelines. And that's what this PR seeks to do with a whole new set of workflow files. See the comments at the top of each one for details.
Type of changes
Checklist
Description
This project is released in two scenarios:
Both of these things take (took) place on
masterbranch. But, this was problematic because these two scenarios differ in lifecycle. One runs automatically, the other, manually. Specifically, development work onmasterwould get whisked away: conflated into the weekly data refresh, no matter if it was really intended to be released.One solution to this is this to have a separate
releasebranch. That way, the weekly data refresh can be applied to it, and not tomaster. Then, master can work on what it needs to without worry of any timelines. And that's what this PR seeks to do with a whole new set of workflow files. See the comments at the top of each one for details.