repository
A project folder whose full history is tracked by version control; in Git, your files plus the hidden .git directory that stores every commit.
In more detail
The files you edit form the working tree, and the .git directory beside them is the database holding every commit, branch and setting. Delete .git and the files stay but the history is gone; copy the folder and the copy has the complete history. A repository on a server that people share is usually a bare repository with no working tree.
Examples
In AWS: A version-controlled store of a project’s files and their full history, usually managed with Git.The course computes DORA metrics by reading a repository rather than asking a survey.When frontend and backend live in separate repositories, contracts drift.git init turns the current folder into a Git repository.The course keeps templates, policies and security gates in the repository so they are reviewed like code.In Terraform: A Terraform repository typically holds one or more configurations and modules. A module can live in its own repository so it can be versioned and released independently. Anyone who clones the repository gets the configuration, but must run terraform init to fetch providers and modules.In this course: Tests must never write into the repository; after a run the working tree should be clean. The repository is also where the review guide and gate commands belong.Related terms
- Git — A free, open-source distributed version control system that records the history of a project as a chain of snapshots.
- commit — A saved snapshot of the whole project in Git, together with its author, committer, time, message and a pointer to the commit before it.
- branch — In Git, a movable name for one commit; committing on the branch moves the name forward to the new commit.
- checkout action — The official action, actions/checkout, that copies the repository onto the runner at the commit being built.
- pull request — A request on a hosting service such as GitHub to merge one branch into another, with a page for review, discussion and automated checks.
- infrastructure as code — Describing servers, networks and other infrastructure in text files that a tool reads to create and change the real thing.
- secret — Any value that grants access, such as a password, access token or private key, and must be kept out of code and version control.
- version control — A system, usually Git, that records every change to a set of files with who made it and why, so work can be reviewed and rolled back.
- codebase — All the source code for a piece of software, usually kept in one or more version control repositories.
- monorepo — A single version-control repository that holds several related projects, such as a web app, an API and their shared libraries.
- .git directory — The hidden directory at the root of a repository where Git keeps all of its data: objects, refs, HEAD, config and the index.
- working tree — The files of a Git repository as they currently exist on disk, which you edit before staging and committing.
- bare repository — A repository that is only the Git database, with no working tree, used as a shared place to push to and fetch from.
- git init — The command that turns the current directory into a Git repository by creating the hidden .git directory.
- image repository — A named collection of related images in a registry, told apart by their tags, such as python with tags 3.12 and 3.13.
- .gitignore — A text file of patterns naming untracked files Git should not report or add, such as build output and logs.
- git clone — The command that copies an entire repository, every commit and branch, from a remote to a new folder on your machine.
- Terraform module — A directory of Terraform files with inputs (variables) and outputs, which other configurations can call to reuse the same infrastructure design.
- code review — A teammate reading a proposed change before it is merged, to understand it, catch mistakes and share knowledge.
Taught in
- Recovering And Removing Data With Git — Microsoft Azure DevOps Engineer Expert (AZ-400) Exam Prep
- One Commit, Four Argo Projects — Certified Argo Project Associate (CAPA) Exam Prep
- Artifacts: Files That Outlive The Pod — Certified Argo Project Associate (CAPA) Exam Prep
- Data Processing Jobs And CronWorkflows — Certified Argo Project Associate (CAPA) Exam Prep
- Argo CD: Components, Applications And Projects — Certified Argo Project Associate (CAPA) Exam Prep
- Sync: Manual Or Automated, Prune And Self-Heal — Certified Argo Project Associate (CAPA) Exam Prep
- Helm, Kustomize And Applications With Several Sources — Certified Argo Project Associate (CAPA) Exam Prep
- ApplicationSets And The App Of Apps — Certified Argo Project Associate (CAPA) Exam Prep
- Final Mock, Review And A Trap Sprint — Certified Argo Project Associate (CAPA) Exam Prep
- A Hotfix At 3 A.M.: Who Wins At 3:05? — Certified GitOps Associate (CGOA) Exam Prep
- Staging Is Gone: Desired State, Declarations And The State Store — Certified GitOps Associate (CGOA) Exam Prep
- Three Edits At 2 A.M.: Drift And Reconciliation — Certified GitOps Associate (CGOA) Exam Prep
- Sixteen Pods, Room For Twelve: The System, Feedback And Continuous — Certified GitOps Associate (CGOA) Exam Prep
- Two Ways Back From 2.5: Rollback The GitOps Way — Certified GitOps Associate (CGOA) Exam Prep
- Terminology Sprint: One Incident, Nine Terms — Certified GitOps Associate (CGOA) Exam Prep
- Seven Steps Called GitOps: The Declarative Principle — Certified GitOps Associate (CGOA) Exam Prep
- Someone Cleaned Up The History: Versioned And Immutable — Certified GitOps Associate (CGOA) Exam Prep
- Twelve Keys To Production: Pulled Automatically — Certified GitOps Associate (CGOA) Exam Prep
- An Hour Without Payments: Continuously Reconciled — Certified GitOps Associate (CGOA) Exam Prep
- Principles Sprint: Six Setups, One Question — Certified GitOps Associate (CGOA) Exam Prep
- Two Clicks Nobody Wrote Down: Configuration And Infrastructure As Code — Certified GitOps Associate (CGOA) Exam Prep
- Friday At Five To Five: DevOps And DevSecOps — Certified GitOps Associate (CGOA) Exam Prep
- What Does CI Still Do? CI, CD And Where GitOps Starts — Certified GitOps Associate (CGOA) Exam Prep
- Related Practices Sprint: One Change, Five Practices — Certified GitOps Associate (CGOA) Exam Prep
- Thursday, With A Way Back: Promotion, Deploy And Release — Certified GitOps Associate (CGOA) Exam Prep
- Three Minutes Of Waiting: Pull Versus Event-Driven — Certified GitOps Associate (CGOA) Exam Prep
- Three Regions By Spring: GitOps Architecture — Certified GitOps Associate (CGOA) Exam Prep
- Patterns Sprint: Eight Needs, One Pattern Each — Certified GitOps Associate (CGOA) Exam Prep
- Three Teams, Three Formats: Manifests And Packaging — Certified GitOps Associate (CGOA) Exam Prep
- A Bucket Nobody Wrote Down: State Stores Beyond Git — Certified GitOps Associate (CGOA) Exam Prep
- A Bake-Off With One Rule: Argo CD And Flux — Certified GitOps Associate (CGOA) Exam Prep
- A Rollback Nobody Heard: Notifications, Observability And CI — Certified GitOps Associate (CGOA) Exam Prep
- Tooling Sprint: The CTO's Shopping List — Certified GitOps Associate (CGOA) Exam Prep
- What Is a Pipeline? — Continuous Integration & Continuous Delivery Pipelines
- Runners: Where Code Executes — Continuous Integration & Continuous Delivery Pipelines
- Keyless Authentication: OIDC to the Cloud — Continuous Integration & Continuous Delivery Pipelines
- Repository Layout for Environments — Continuous Integration & Continuous Delivery Pipelines
- Container Images The Exam Way — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Helm: Install, Upgrade And Roll Back — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Users, Groups and Roles — Cloud Infrastructure & Hyperscaler Architecture
- Policies and Least Privilege — Cloud Infrastructure & Hyperscaler Architecture
- The Danger of Long-Lived Keys — Cloud Infrastructure & Hyperscaler Architecture
- Infrastructure as Code (Handover to Terraform) — Cloud Infrastructure & Hyperscaler Architecture
- Workload Identity Federation: Eliminating Static Keys — Cloud Security & DevSecOps Engineering
- Cross-Account AssumeRole Chains & Temporary STS — Cloud Security & DevSecOps Engineering
- Shift-Left Security Principles & Automated Pipeline Gates — Cloud Security & DevSecOps Engineering
- Pre-Commit Secret Scanning with Gitleaks & Entropy — Cloud Security & DevSecOps Engineering
- Static Application Security Testing with Semgrep — Cloud Security & DevSecOps Engineering
- Software Composition Analysis with Trivy — Cloud Security & DevSecOps Engineering
- Supply Chain Security: SBOMs & Cosign Signing — Cloud Security & DevSecOps Engineering
- Static IaC Scanning: Linting Terraform with Checkov — Cloud Security & DevSecOps Engineering
- Policy-as-Code Architecture: OPA & Rego Syntax — Cloud Security & DevSecOps Engineering
- Enforcing OPA Guardrails on Terraform Plan Payloads — Cloud Security & DevSecOps Engineering
- Throughput: Change Lead Time And Deployment Frequency — DevOps & Site Reliability Engineering
- Instability: Change Fail Rate And Deployment Rework Rate — DevOps & Site Reliability Engineering
- Codebase And Dependencies — DevOps & Site Reliability Engineering
- Admin Processes And The Open Source Update — DevOps & Site Reliability Engineering
- Pipelines And GitOps Context — DevOps & Site Reliability Engineering
- Monorepo Architecture: Workspaces & Turborepo — Production Full-Stack Engineering
- Why Version Control, And Why Git Won — Advanced Git Internals & Distributed Workflows
- Installing Git, And Telling It Who You Are — Advanced Git Internals & Distributed Workflows
- A Repository Is A Folder With A Memory — Advanced Git Internals & Distributed Workflows
- What A Commit Really Is — Advanced Git Internals & Distributed Workflows
- The Three Areas: Working Tree, Index, Repository — Advanced Git Internals & Distributed Workflows
- Staging Deliberately: status, add, add --patch — Advanced Git Internals & Distributed Workflows
- Committing, And What A Good Message Says — Advanced Git Internals & Distributed Workflows
- Conventional Commits — Advanced Git Internals & Distributed Workflows
- Reading History: log, show And diff — Advanced Git Internals & Distributed Workflows
- Ignoring Files, And The Tracked File Trap — Advanced Git Internals & Distributed Workflows
- A Branch Is A Moving Pointer — Advanced Git Internals & Distributed Workflows
- HEAD, And Why Detached HEAD Is Not An Error — Advanced Git Internals & Distributed Workflows
- Merging: Fast Forward Or A Merge Commit — Advanced Git Internals & Distributed Workflows
- Rebase: The Same Work, A Different History — Advanced Git Internals & Distributed Workflows
- Undoing: restore, reset, revert And stash — Advanced Git Internals & Distributed Workflows
- What A Remote Actually Is — Advanced Git Internals & Distributed Workflows
- Clone, Forks, Push, And The Upstream Branch — Advanced Git Internals & Distributed Workflows
- Fetch Is Not Pull — Advanced Git Internals & Distributed Workflows
- The Pull Request, And Branch Naming — Advanced Git Internals & Distributed Workflows
- Reviewing Code Well — Advanced Git Internals & Distributed Workflows
- Resolving A Conflict, Line By Line — Advanced Git Internals & Distributed Workflows
- Investigating History: blame, bisect And worktree — Advanced Git Internals & Distributed Workflows
- Tags And Releases — Advanced Git Internals & Distributed Workflows
- Control Plane: etcd, API Server, Scheduler, Controllers — Kubernetes: Production-Grade Container Orchestration
- kubeadm, High Availability And Cluster Lifecycle — Kubernetes: Production-Grade Container Orchestration
- Package The Service As A Helm Chart — Kubernetes: Production-Grade Container Orchestration
- Argo CD Applications And Flux Reconciliation — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: GitOps Drift And Controller Failures — Kubernetes: Production-Grade Container Orchestration
- Shipping: scripts, entry points and git — Hands-on Python: Complete Video Course & Book
- Why Secrets Leak — Application Security & Threat Modeling for Engineers
- Dependency Risk And Typosquatting — Application Security & Threat Modeling for Engineers
- Secret Scanning — Application Security & Threat Modeling for Engineers
- Vulnerabilities And Attack Surfaces — CompTIA Security+ (SY0-801) Exam Prep
- Initialising The Working Directory — Infrastructure as Code with Terraform
- Versioning And Pinning Modules — Infrastructure as Code with Terraform
- Native Testing With Tftest Files — Infrastructure as Code with Terraform
- Testing The Filesystem — Automated Testing, TDD & Quality Engineering
- Code Review As A Quality Gate — Automated Testing, TDD & Quality Engineering
- What To Automate Away — Automated Testing, TDD & Quality Engineering
- Infrastructure As Code, And One Workflow For Every Platform — HashiCorp Terraform Associate (004) Exam Prep
- Providers: How Terraform Reaches Every API — HashiCorp Terraform Associate (004) Exam Prep
- State: Terraform's Memory Of What It Built — HashiCorp Terraform Associate (004) Exam Prep
- Resources, Data Sources And The References Between Them — HashiCorp Terraform Associate (004) Exam Prep
- Input Variables, Outputs, And Which Value Wins — HashiCorp Terraform Associate (004) Exam Prep
- Where Modules Come From — HashiCorp Terraform Associate (004) Exam Prep
- Module Scope: What Goes In, What Comes Out — HashiCorp Terraform Associate (004) Exam Prep
- The Local Backend, And Workspaces On One Machine — HashiCorp Terraform Associate (004) Exam Prep
- One Edited File, Six Rebuilt Steps: Layers, Cache And Flat Images — Docker Certified Associate (DCA) Exam Prep
- Three Names, One Image: Listing, Formatting, Tagging And Pruning — Docker Certified Associate (DCA) Exam Prep
- Our Own Registry: Deploy, Push, Pull, Search And Delete — Docker Certified Associate (DCA) Exam Prep
- One Comma, No Engine: Installing And Configuring Docker Engine — Docker Certified Associate (DCA) Exam Prep
- Port 2375, Open To The Office: Engine TLS And Registry Certificates — Docker Certified Associate (DCA) Exam Prep
- Two Of Everything: Deploying, Sizing And Backing Up UCP And DTR — Docker Certified Associate (DCA) Exam Prep
- Installation Sprint: Eight Configuration Calls — Docker Certified Associate (DCA) Exam Prep
- Four Questions From The Auditor: Swarm Security, Autolock And Content Trust — Docker Certified Associate (DCA) Exam Prep
- The Upgrade That Broke Nginx: Packages, Repositories And Pins On Both Families — CompTIA Linux+ (XK0-006) Exam Prep
- The Release Tag That Never Left The Laptop: Git Branches, Remotes, Tags And History — CompTIA Linux+ (XK0-006) Exam Prep
- A New Depot By Friday: OpenTofu, Cloud-init, Pipelines And Kubernetes — CompTIA Linux+ (XK0-006) Exam Prep
- Patched On Paper: Missing Updates, Broken Chains, Old Protocols And Open Doors — CompTIA Linux+ (XK0-006) Exam Prep
- RPM, YUM, DNF And Zypper — LPIC-1 Linux Administrator (101-500 and 102-500) Exam Prep
References
- Pro Git: About version control
- Git glossary
- Git documentation: git-init, creating a repository
- Git: Getting a Git repository
- Git glossary: repository
- git-clone documentation
Certification courses
- AZ-400 course and practice exam: Microsoft Azure DevOps Engineer Expert
- CAPA course and practice exam: Certified Argo Project Associate
- CGOA course and practice exam: Certified GitOps Associate
- CKAD course and practice exam: Certified Kubernetes Application Developer
- CompTIA Security+ course and practice exam: SY0-801
- Terraform Associate course and practice exam: HashiCorp Terraform Associate (004)
- DCA course and practice exam: Docker Certified Associate
- CompTIA Linux+ course and practice exam: XK0-006
- LPIC-1 course and practice exam: Linux Administrator (101-500 and 102-500)