It occurred to me yesterday while @RaggedStaff and I were speaking, would it make things easier to merge these by doing one or both of the following?
Move these notes into the datafoodconsortium/.github repository; that way it will only require one review before merging, rather than the 2 reviews required by standard.
Create a persistent branch, such as projects/tech-meetings, which could be linked to in the Tech Meetings Project Board, rather than pointing to the main or master branch; that way branch protections can be fine-tuned or entirely removed regardless of which repository the notes are in. I'm using the example projects/tech-meetings here with slash branches as a prefix category (potentially w/ branches projects/main and projects/prototype added now or later), but that's not necessary.
I've prepped a change to the .github repo I can submit as a PR, with all the latest changes including the commits @lecoqlibre added yesterday, so just say the word and I can get that ball rolling.
RachL
commented
1 month ago
It occurred to me yesterday while @RaggedStaff and I were speaking, would it make things easier to merge these by doing one or both of the following?
datafoodconsortium/.githubrepository; that way it will only require one review before merging, rather than the 2 reviews required bystandard.projects/tech-meetings, which could be linked to in the Tech Meetings Project Board, rather than pointing to themainormasterbranch; that way branch protections can be fine-tuned or entirely removed regardless of which repository the notes are in. I'm using the exampleprojects/tech-meetingshere with slash branches as a prefix category (potentially w/ branchesprojects/mainandprojects/prototypeadded now or later), but that's not necessary.I've prepped a change to the
.githubrepo I can submit as a PR, with all the latest changes including the commits @lecoqlibre added yesterday, so just say the word and I can get that ball rolling.