Getting GitHub Actions into your pipeline is where it starts paying off - automated, repeatable and reviewed. Here is a working integration and the habits that keep it reliable.
A working pipeline snippet
Deploy to AWS using OIDC - no long-lived secrets.
permissions: { id-token: write, contents: read }
steps:
- uses: aws-actions/configure-aws-credentials@v4
with:
role-to-assume: arn:aws:iam::1234:role/gha-deploy
aws-region: eu-west-1
- run: aws s3 sync ./dist s3://acme-site --deleteDo this
- Pin actions to a commit SHA and review third-party actions before use
- Use OIDC for cloud auth and set minimal permissions blocks
- Cache dependencies and split long jobs with a matrix
Avoid this
- Using un-pinned third-party actions (tag can move under you) - pin to a SHA
- Storing cloud keys as secrets instead of using OIDC
- Over-broad GITHUB_TOKEN permissions; scope them per job
Want senior help putting GitHub Actions to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.