What is Git
Also known as: version control, git repository, git repo
Definition
Git is free version control software: it saves a version of the code each time a developer commits, so you see who changed what and can go back.
Why it matters
Your code is a business asset, and Git's history is the record of what was built, by whom and when.
Common mistakes
Letting a developer keep the code in a personal account, so the business cannot reach it when the developer leaves.
Related terms
Worked exampleIllustration
One fix to a booking form, from branch to rollback
One commit, its parts marked
- Commit IDa1b2c3d
- AuthorThe contractor
- DateTuesday 14:05
- MessageFix phone field validation
- Files changedThe booking form
- Branchfix-booking-phone
Owned by
The clinic's GitHub organization
Not inside
The database, uploaded files and passwords
Steps
The developer creates a branch named after the change.
The developer commits twice, with messages such as "Fix phone field validation" and "Add confirmation text".
A pull request is opened, and a second person reviews it.
The branch is merged into main, and the site is deployed.
The next day a problem shows up, so the developer reverts that merge and deploys again, and the old form is back.
Decision: The owner, who owns the GitHub organization, sees the whole history and who did what, even after the contractor leaves.
Nothing was lost at any step, and the history stays with the business, not with the developer.
Illustration
How it works
Every saved version, and the way back
- The form before the fix
- Commit: phone field check, on a branch
- Commit: confirmation text, on a branch
- Merged into main and deployedhas the bug
- The merge reverted, the old form back
Live site works. Reverting the merge adds one more version that undoes it. The old form is back, and the history still shows what happened and who did it.
Definition
Git is a version control system, one of several, that keeps the full history of a project's code. It records a version, called a commit, each time a developer marks a step as done, and good developers commit many times a day. It records nothing by itself when a file is saved. The history lives in a repository. Work happens on branches, separate lines where a change is built without touching the main code, and a branch is merged back after review, usually through a pull request on a hosting service. Git is free, open source software that runs on the developer's computer. GitHub, GitLab and Bitbucket are separate services that host Git repositories online and add reviews, permissions and team features. Git dates from 2005: Pro Git records that the relationship between the Linux kernel community and the company behind BitKeeper, the tool they used, broke down and its free of charge status was revoked, which led Linus Torvalds and the Linux community to build their own tool.
Why it matters
The owner's question is who holds the repository: the code should live in an organization account the business owns, with developers invited as members, so a contractor who leaves takes nothing with them. GitHub's Free plan, which organizations can use, includes unlimited private repositories and unlimited collaborators, so owning the repository costs nothing. Git also lets a team go back to the last working version quickly when a change breaks something, although the older version still has to be deployed. And Git is not a backup of everything: it holds code, not the database, uploaded files or passwords, which need their own backup.
Directly related: Deployment, Staging, Production.
Improvement tips
- Keep the code in an organization account the business owns, and invite developers as members.
- Turn on two step verification for the owner's login to the code hosting service.
- Remove a contractor's access the day the work ends.
- Write in the contract that the code and the repository belong to the business.
- Ask for a simple branch per change, merged after review. Vincent Driessen, author of the popular git-flow model, wrote in 2020 that teams delivering continuously, as most web apps do, should adopt a much simpler workflow.
Common mistakes
- Committing passwords, API keys or configuration secrets into a repository.
- Writing vague commit messages such as "fixed stuff", which make the history useless.
- Treating Git as the backup of everything, while the database and uploaded files have no backup of their own.
- Working directly on the main branch with no review.
Related terms
Deployment
Deployment, or a deploy, is the step where a new version of a site or app goes live: the code is built, tested and moved to a server, with a quick way back.
Staging
Staging is a private copy of a website or app, kept as close to the live one as possible, where a change is checked before it reaches customers.
Production
Production is the live version of your website or app, the one real customers use with real data. Any fault there costs sales, so it changes only after testing.
Technical Debt
Technical debt is the future work created by choosing a quick code solution today over the right one. Unpaid, the interest builds and development slows.
Vibe Coding
Vibe coding is building software by telling an AI what you want, running what it writes and never reading the code. Great for a prototype, risky with customers.
Quick check
Your contractor is leaving. Which setup means the code stays with you?
Choose an answer
Frequently asked questions
Do I need to understand Git before I start my business?
When does Git first become relevant for a new business?
What does Git cost?
Who should own the account where our code is stored?
Why does Git matter for a business already running?
What goes wrong when a developer does not use Git?
How do I move existing code into Git?
How does Git protect me from depending on one contractor?
What does Git actually mean in plain words?
Is Git risky or complicated for an owner who is not technical?
Does Git save everything automatically?
What is the difference between Git and GitHub?
Sources: Scott Chacon and Ben Straub, Pro Git, 2nd edition, including A Short History of Git (git-scm.com/book), read 23 September 2026, GitHub Docs, About organizations (docs.github.com), read 23 September 2026, GitHub, Pricing (github.com/pricing), read 23 September 2026, Vincent Driessen, A successful Git branching model, note of reflection of 5 March 2020 (nvie.com)
Last reviewed: 2026-09-23
I have worked with
- Google for Startups
- House of Business, Sderot Municipality
- Microsoft Reactor
- GameReady
- Eclipse Capital
- SderoTech
- IUCEL
- Resilience & Health Innovation Hub
- International Resilience Institute of Sderot
- Google for Startups
- House of Business, Sderot Municipality
- Microsoft Reactor
- GameReady
- Eclipse Capital
- SderoTech
- IUCEL
- Resilience & Health Innovation Hub
- International Resilience Institute of Sderot
What Clients Say
From different fields, at different stages of business
Dan Manto
Eclipse Capital
Real Estate Investment and Finance, USA
Arty McLabin
GameReady
Game Development Education and Outsourcing, International

Anna
Beautician
After I finished a cosmetology course at a leading company, I was confused. I didn't know how to open a business, what to sell from home, or how to bring in clients. Since I reached out to Mobius, everything has changed. We built an organized plan with clear steps and no unnecessary risks. Today I see results, and I'm growing and developing every month.

Mark
Massage therapist, Gan Yavne
When I finished a massage course, I imagined a different world. I found out it's a hard field, and financial stability isn't easy to find. When I came to Mobius, something changed. We started an organized process and built a business plan. Without Mobius? I probably would have given up. Today I believe in myself and in my own path.
Tech decisions bigger than your team?
Alex helps Israeli businesses choose technology that fits the business, not the hype. The first call is free.
+972 055-248-6151. Better on WhatsApp: I am in meetings most of the day and answer as soon as I am free. Other ways to reach me