GitHub Actions turns a repository change into a repeatable delivery path. Instead of handing work between people, a continuous integration pipeline moves code through predefined checks and build steps. section 1.0 section 2.3
A YAML workflow defines when the pipeline runs, which jobs it performs, and what happens when something fails. Jobs contain ordered steps, may depend on one another, and either run commands or invoke reusable actions. section 2.3
A first build pipeline can stay deliberately small:
- Set up the Go environment. section 2.3
- Check out the repository code. section 2.3
- Build a binary. section 2.3
- Copy the binary into an artifacts directory. section 2.3
- Upload the artifact to GitHub. section 2.3
A repository build workflow
Create .github/workflows/pipeline.yml and trigger it on pushes to main. A build job running on ubuntu-latest can use actions/setup-go@v2 with Go ^1.18, actions/checkout@v2, make build, shell commands for copying files, and actions/upload-artifact@v2 for the resulting api binary. section 2.3
