lesson 3 of 3 · github actions for model checks — what a green check does and doesn't meangithub actions for model checks — what a green check does and doesn't meanlesson 3 of 3 · github actions for model checks — what a green check does and doesn't meangithub actions for model checks — what a green check does and doesn't meanlesson 3 of 3 · github actions for model checks — what a green check does and doesn't meangithub actions for model checks — what a green check does and doesn't meanlesson 3 of 3 · github actions for model checks — what a green check does and doesn't meangithub actions for model checks — what a green check does and doesn't meanlesson 3 of 3 · github actions for model checks — what a green check does and doesn't meangithub actions for model checks — what a green check does and doesn't meanlesson 3 of 3 · github actions for model checks — what a green check does and doesn't meangithub actions for model checks — what a green check does and doesn't meanlesson 3 of 3 · github actions for model checks — what a green check does and doesn't meangithub actions for model checks — what a green check does and doesn't meanlesson 3 of 3 · github actions for model checks — what a green check does and doesn't meangithub actions for model checks — what a green check does and doesn't meanlesson 3 of 3 · github actions for model checks — what a green check does and doesn't meangithub actions for model checks — what a green check does and doesn't meanlesson 3 of 3 · github actions for model checks — what a green check does and doesn't meangithub actions for model checks — what a green check does and doesn't meanlesson 3 of 3 · github actions for model checks — what a green check does and doesn't meangithub actions for model checks — what a green check does and doesn't mean
A workflow YAML has three top-level parts: name, the trigger, and
jobs. Fill in the key that decides WHEN the workflow runs — the
one you'd set to [pull_request] so the gate fires before merge,
not after.
Key: