Git, GitHub and GitHub Actions for Developers

09:00 – 10:15

All the Git you'll actually use

commits branches and merges, resolving a real conflict, undo and recover with reflog

Takeaway The working set compressed into one sitting: commit, branch, merge, a genuine conflict resolved, and a hard reset recovered. Enough Git to trust yourself for the two days ahead.

10:30 – 11:45

Open a pull request that survives review

push and clone, small PRs, review etiquette, suggested changes

Takeaway A pull request opened, reviewed and merged, including giving a real review on someone else's change.

12:00 – 13:00

Protect main like a team that ships

branch protection, required checks, CODEOWNERS

Takeaway A main branch nobody can break by accident, including you, and demonstrated by trying.

14:00 – 15:15

Get your first pipeline green

workflows jobs and steps, your first workflow, using and configuring actions, checking out code

Takeaway A first workflow written, run and read end to end, then a more realistic one reacting to every push, deliberately broken and diagnosed from the logs.

15:30 – 17:00

Trigger exactly when you want

events and activity types, event filters, parallel vs sequential jobs, expressions and context objects

Takeaway Workflows that fire on precisely the pushes and pull requests you choose, including the fork edge cases, and cancelling or skipping runs on purpose.

09:00 – 10:15

Artifacts, outputs and faster builds

job artifacts, job outputs across jobs, dependency caching and invalidation

Takeaway A build that hands its artifact and outputs to the next job, and finishes visibly faster on a warm dependency cache.

10:30 – 11:45

Secrets and environments, handled properly

environment variables, secrets, repository environments

Takeaway A workflow talking to a real database with nothing sensitive committed, values flowing from secrets and per-environment configuration.

12:00 – 13:00

One workflow, many jobs

conditional steps and jobs, continue-on-error, matrix strategies, reusable workflows

Takeaway One matrix run testing across versions in parallel, failures contained deliberately, and a reusable workflow with inputs and outputs called from another workflow.

14:00 – 15:15

Containers and custom actions

jobs in containers, service containers, composite actions, JavaScript and Docker actions

Takeaway A job running in your own container against a service database, and a composite action you wrote, stored in a repository, usable by anyone.

15:30 – 17:00

Lock it down, release through the pipeline

script injection attacks, GITHUB_TOKEN and permissions, OpenID Connect to the cloud, tags releases and approvals

Takeaway The pipeline hardened (injection closed, token scoped, cloud access via OIDC with no long-lived keys), and a tagged release cut through an environment that requires approval.