This was a discussion/outline that I should have done prior to starting to just code it up with the REST API, since that would have made it very obvious that one of the main things we want to do (convert cards/notes to issues) isn't possible via the v3 API. So in forcing myself to go through the actual steps that we're going to follow in using the v4 API (GraphQL), I'm hoping any glaring holes in technical possibilities show up sooner rather than later.
I'll be adding to this issue, and specifying endpoints/actions to the extent possible, though the basic outline of the actions against the API will be as follows:
The user clones the repo that has the github actions set up.
The user generates a personal access token with full repo scope and adds that as a secret called TOKEN.
The user manually runs the github action.
The github action creates a home repo based on the school.yml template
The github action creates a deliverables project board
The github action creates columns on the deliverables project board, based on the school.yml template items
The github action creates cards in the TODO column of the deliverables project board based on the school.yml template items.
This was a discussion/outline that I should have done prior to starting to just code it up with the REST API, since that would have made it very obvious that one of the main things we want to do (convert cards/notes to issues) isn't possible via the v3 API. So in forcing myself to go through the actual steps that we're going to follow in using the v4 API (GraphQL), I'm hoping any glaring holes in technical possibilities show up sooner rather than later.
I'll be adding to this issue, and specifying endpoints/actions to the extent possible, though the basic outline of the actions against the API will be as follows:
TOKEN
.school.yml
templateschool.yml
template itemsschool.yml
template items.