Running it yourself
Whatever trigger you chose, you can always start GrillMyCode by hand. That's useful for regenerating a student's questions, trying a different setting, or running an assessment after the deadline.
Start a run
- Open the student's repository and go to the Actions tab.
- In the list on the left, select GrillMyCode, or the name you gave the workflow.
- Select Run workflow, then the green Run workflow button.
The run works exactly like an automatic one. The student's existing issue is updated with the new questions, and the PDF is replaced.
To run a milestone assessment again, choose the tag from the Use workflow from list before starting the run.
It doesn't matter who starts the run. The assessment always belongs to the student who owns the repository, even when you start it yourself.
More than one set of questions
An assignment can have more than one GrillMyCode workflow, such as a checkpoint and a final review that you run at different times. Give each one a different Workflow name on the Workflow Wizard's Delivery step. Each name gets its own issue, PDF and private answer key, so running one never replaces the other's questions. Two workflows with the same name share them. See the Two sets of questions recipe.
Change a setting for one run
Normally, the settings in the workflow file apply to every run, and changing one means editing the file. You can instead put chosen settings on the Run workflow form, pre-filled with their usual values. Whatever you change there applies to that one run only.
Set this up in the Workflow Wizard's Manual runs step. Answer Yes to its first question to choose settings for the form, or No if you'd rather every run used the workflow file's settings. Under Yes, these are ticked by default:
- preview only, which lists the files a run would assess and stops, without generating questions; see Trying your patterns first
- AI model
- number of questions
- question emphasis
- assignment brief files
- instructor instructions
- extra files to leave out
- files to bring back
- keep code comments
Pick only settings you actually expect to change; a short form is easier to use.

What to keep off the form
Anyone who can run the workflow can fill in the form, and that includes the student whose work is being assessed. The Wizard therefore never offers:
- Secrets and keys. What's typed in the form isn't secret.
- Include answers. It would give students a "show me the answers" button.
- Settings that could quietly empty the assessment, such as which commits are compared, or whose commits to skip.
A preview is on the form because it isn't quiet: the run says plainly that it was a preview, and it leaves the student's existing questions alone.
The assignment brief setting is on the form too. A student could point it at a file they wrote, but that only steers the topics, and the run summary lists the files it read. Untick it if you'd rather the brief could only be changed in the workflow file.
Go deeper: Triggers in depth: how the form's values reach the workflow, and why, and question sets · Recipe: Manual run overrides