Page History

...

1. Do step 'CLI - c.' (other) Find (or make own) a gh extension creating skeletal framework like creating a new project, and we can use that to create a simple project.

   Jira
   server SLAC National Accelerator Laboratory serverId 1b8dc293-975d-3f2d-b988-18fd9aec1546 key EEDSWCM-77

2. Think about if we host the github runner on self-host organization level, that it will be responsible for fulfilling all of the requests of developers triggering the workflow. 
   1. This can be problematic if requests are overwhelming the build system which can lead to a large wait time for builds
   2. Instead maybe we want a 'build system' that gets run each time a developer requests something, in that case we would have to make a runner self-hosted on each repo. Or we can keep the runner on github since we have enterprise, the only concern would be if there are any external limitations (i.e. any restrictions on what we can run like if a test can only be ran on certain hardware)
3. Complete buildroot github action workflow