Suggest an editImprove this articleRefine the answer for “What is a Git workflow?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**A Git workflow** is a team's set of rules and agreements for creating branches, making changes, and shipping releases in Git. **Key point:** a Git workflow is not a built-in Git feature, it is an agreement within the team.Shown above the full answer for quick recall.Answer (EN)Image**A Git workflow** is a **set of rules and agreements** for *how a team works with Git*: what branches exist, who creates them and when, how changes are merged in, and how releases are shipped. In simpler terms: *A Git workflow answers the question "HOW do we use Git as a team."* --- ## Why a Git workflow is needed Without a workflow: - everyone works however they want - conflicts and broken branches appear - it is hard to tell what is ready for release With a workflow: - everyone understands **where to write code** - it is clear **how and where to merge changes** - the repository history is understandable - there are fewer mistakes and less chaos --- ## What a Git workflow usually describes A Git workflow defines: - what branches exist (`main`, `develop`, `feature/*`, etc.) - which branch to create new branches from - how changes are made (merge or rebase) - when and by whom pull requests are made - how releases and hotfixes go out --- ## A simple example A team agreed on: - `main` holds only stable code - new tasks go into separate `feature` branches - code reaches `main` **only through a pull request** - a review is mandatory before merging That is a **Git workflow**. --- At interviews you are most often asked about: 1. **Centralized workflow**, everyone works in almost the same branch 2. **Feature Branch workflow**, each task in its own branch 3. **Gitflow**, a strict scheme with `develop`, `release`, `hotfix` 4. **Trunk-based development**, frequent small changes to `main` It is important not just to know the names, but to **understand why they are needed and when they apply**. --- ## Important point for an interview A Git workflow is **not a built-in Git feature** It is an **agreement within the team** Git **does not forbid** breaking the workflow, it just provides the tools. --- ## Short answer for an interview > **A Git workflow is the way of working with Git that a team has agreed on: rules for creating branches, making changes, and merging code that help organize team development.**For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.