You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
issues could be automatically created with something like https://github.com/imjohnbo/issue-bot, which would allow for locking down the issues in make-models-fair/coordination but then creates a number of extra problems such as needing a workaround for adding models not in the list
same deal as with creating repos, a workflow that gets triggered when an issue is created/relabeled to update model_status.csv with one requirement being a unique identifier shared between the repo/planning issue/models list, which the <name-[name/etal]-year> is a good candidate for
redeploying hugo site
maybe have a scheduled workflow that runs nightly IF there were changes to the list (in addition to on push to the mainline)
issue creation:
<author-year>with the title being dynamically pre-filledrepo creation:
gh repo create <TITLE> --template="make-models-fair/model-template"in a workflow just like https://github.com/make-models-fair/coordination/blob/main/.github/workflows/new-repo-request.yml. Where<TITLE>should be available in the hook payload/contextupdating models list
model_status.csvwith one requirement being a unique identifier shared between the repo/planning issue/models list, which the<name-[name/etal]-year>is a good candidate forredeploying hugo site