Git, Infrastructure as Code and Deployment Pipelines (CI/CD) with Vibe Coding

Teams that struggle to ship rarely have a tooling problem. They have a handoff problem: the source code sits in one person's head, the infrastructure sits in another person's terminal history, and a deployment is the Friday afternoon everyone has learned to dread. This two-day programme joins version control, infrastructure and delivery into a single workflow, adds a disciplined way of working with an AI coding assistant, and then has every participant run the whole thing end to end. That is a different experience from studying any one of the parts. Day one is Git, taken well past the three commands most people stop at. Day two adds Infrastructure as Code, vibe coding and a pipeline that carries a commit through to a deployment.

Programme Agenda

Git Foundations and Repository Setup

What a commit really is, why the staging area exists, and how a local repository relates to a remote one. Starting a repository from nothing, connecting it to a hosted remote, and reading the history well enough to answer the question that matters in an incident: what changed, and when. Hands-on: create a repository, build a run of commits and read the project history back.

Branching Strategies and Working as a Team

Feature, release and hotfix branches, with the honest trade-offs rather than a push toward whichever model is fashionable this year. Push, pull and fetch, including the fetch versus pull difference behind most early confusion. Working beside colleagues without overwriting their changes. Hands-on: run a multi-branch workflow against simulated teammates.

Merge Conflicts, Resolved Calmly

Why conflicts happen, which is rarely the reason people assume. Reading conflict markers without guessing, three-way merges, and a repeatable resolution routine that never quietly drops a colleague's work. Hands-on: cause conflicts on purpose, resolve them and confirm nothing was lost.

Rebase, Cherry-Pick and a History Worth Reading

Rebase against merge, and when each is the right call. Interactive rebase to tidy work before review, and cherry-pick for the cases that genuinely need it. Keeping a history a colleague can still use six months from now. Hands-on: rebase a working branch, resolve what it raises and prepare the change for a pull request.

Infrastructure as Code Fundamentals

Why describing infrastructure in a file beats configuring it by hand, put in terms of the failures it prevents. Declarative against imperative approaches, and idempotence as the property that makes automation trustworthy. Keeping infrastructure under the same version control as application code, using Terraform or OpenTofu style tooling. Hands-on: write a basic infrastructure configuration and manage it through Git.

Vibe Coding for Infrastructure and Development

AI-assisted development in practice: prompt-driven work, and the review discipline that separates useful output from plausible-looking output. Using an assistant to write, explain, refactor and troubleshoot code and configuration while keeping the result reviewable by someone who was not in the room. Where these tools are genuinely fast, and where accepting their output unread creates work instead of saving it. Generated code is treated as untrusted until it has been reviewed, tested and run through the pipeline.

Building Your First CI/CD Pipeline

Pipeline stages and triggers, and what should happen automatically against what still needs a person. Connecting source control to build and deployment on a hosted pipeline tool such as GitHub Actions or GitLab CI. Separating environments so a deploy to staging cannot turn into a deploy to production by accident. Hands-on: configure a pipeline that runs from a source commit through build to deployment.

End-to-End Project: From Commit to Deployment

Teams run the full workflow: branch, change the infrastructure configuration, open a pull request, merge, and watch the pipeline build and deploy. Then they break it on purpose. Diagnosing the configuration and pipeline failures that turn up most often in real projects, and finishing with a CI/CD workflow that works.

Learning Outcomes:
Use Git for branching and collaboration at team scale, not as a backup tool
Choose a branching strategy and resolve merge conflicts without losing anyone's changes
Write and version-control Infrastructure as Code using declarative, idempotent configuration
Apply AI-assisted coding workflows while keeping code reviewable and maintainable
Build an automated CI/CD pipeline from source control through to deployment
Troubleshoot the development, build and deployment failures that occur most often in practice
Deploy an application end to end through a workflow the team has run for itself

Duration: 2 Days (16 Hours)
Training Hours: 9:00 AM to 5:00 PM
Level: Intermediate
Training Mode: Physical, Online, or Hybrid
HRD Corp SBL-KHAS Claimable
Certificate of Completion included

Related programmes:
CI/CD and DevOps Culture (one day going deeper on pipeline design, testing layers and delivery metrics)
Infrastructure as Code (two days going deeper on state, modules and environment separation)
DevSecOps and Cloud Security Hardening (for securing the pipeline and the cloud account once the workflow is running)
Build Business Apps with AI (Vibe Coding) (for colleagues who are not engineers but want to build working tools with AI)

More in Cloud, DevOps and Platform Engineering

• DevSecOps and Cloud Security Hardening · All levels, 2 days
• Cloud Engineering Foundations (AWS and Azure) · Beginner, 2 days
• Containers and Kubernetes Basics · Beginner, 2 days
• CI/CD and DevOps Culture · All levels, 1 day
• Infrastructure as Code · All levels, 2 days