Why represent build and deploy as separate GitHub Actions jobs?
Separating jobs guarantees deployment runs even when the build fails.
Each job creates a separate workflow file automatically.
GitHub Actions requires every command to be placed in a different job.
They become distinct pipeline phases whose ordering and success dependency can be controlled explicitly.