←  All terms
G
QA & Deployment

Git

Git is a distributed version control system that records file changes and supports collaborative development.

Git is a distributed version control system that records file changes and supports collaborative development. Automated checks speed up validation but do not replace focused manual testing of critical user journeys. The concept is closely related to CI/CD and Deployment.

Read more

CI/CD

Deployment

Webflow Cloud

Rollback

FAQ

Git

What typical mistakes happen when working with Git?
Common issues are oversized commits with vague messages, long-lived branches with painful merges, and credentials that accidentally end up in the repository. Missing protection rules for the main branch also let unreviewed changes through. Small, well-described commits and short branches reduce these risks. Published secrets count as compromised and must be replaced.
How are Git and CI/CD connected?
A push or merge in Git often serves as the trigger for CI/CD pipelines. These build the project, run tests, and publish a new version on success. That keeps the path from commit to deployment traceable. The prerequisite is clear branch rules, for example that only reviewed code reaches the main branch.
What is the difference between Git and a repository hosting service?
Git is the software that manages versions locally and in distributed fashion. A repository hosting service builds on it with central storage, permissions, pull requests, and automation. Git works without such a service. For teams, though, the central platform is where reviews and CI/CD pipelines get triggered.
Why does a web project need Git?
Git makes every change to the code traceable and reversible. Teams work in parallel branches, combine changes through merges, and review them beforehand. When something breaks, an earlier state can be restored. Without version control, history depends on file names and memory, which quickly becomes unmanageable with several contributors.