northdan.
Vezi pagina în română

IT Glossary

What is Git?

The standard version control system for code: every change permanently recorded — who, what, when and why.

A software project's code changes thousands of times over its life, and Git is the system that keeps the ledger: every modification is recorded as a "commit" with author, date and description; the complete history stays browsable at any point in the past; and developers work in parallel on branches that merge back under control. It is the industry's absolute standard — platforms such as GitHub, GitLab and Bitbucket host the repositories and add collaboration on top: code review, discussions, automation — so universal that its absence at a vendor is a diagnosis, not a preference. The reason it belongs in a business glossary is ownership: the Git repository is the concrete form of your property over software you paid to have built. The healthy contract clause for custom development reads: code delivered as repository access — ideally on an account your company owns or controls with full rights — with complete history, not a ZIP archive at project end. That history has practical value: a new vendor understands a readable project many times faster, disputes about when something broke get exact answers, and quality audits work from facts. A small cultural bonus: hearing that some software "is on GitHub" means public code, often open source; your private project being hosted there means only that the repository lives on the platform — visible strictly to whoever was granted access.

Let’s talk about your project

Message us on WhatsApp or send an email — you talk directly to a developer.

office@northdan.com · +40 752 070 247

Why it matters for your business

Complete history, short disputes

Every line of code has an author, a date and a reason — "when and why did this change" gets a documented answer, not recollections.

Nothing lost, everything reversible

Any version in history can be restored — failed experiments and accidental deletions stop being catastrophes.

Civilized handovers

Repository access makes changing vendors a normal technical process — not archaeology through ZIP archives and old emails.

Frequently asked questions

What exactly should our contract say about Git?

Three things: the repository hosted on an account where your company is owner or holds full rights (you grant the vendor access, not the reverse), delivery defined as repository access with complete history, and continuous delivery there throughout the project — not "you'll get the code at the end." It costs nothing and spares you the argument on separation day.

What is the difference between Git and GitHub?

Git is the tool — the version control system, free and open source; GitHub is the most popular platform hosting Git repositories, adding collaboration: reviews, permissions, automation. Alternatives include GitLab and Bitbucket. As a client, which platform matters little — what matters is that the repository exists and you have access to it.

Can a non-technical person see anything useful in a project's Git repository?

Surprisingly much: the rhythm of commits shows whether work is steady or panic bursts before demos, the commit messages reveal discipline or chaos, and the presence of approved pull requests shows quality control in action. You are not reading the code — you are reading the team's behavior.