Skip to content
IconMind

Developer Tools

Version control icons

30 icons in the version-control group of Developer Tools: Branch, Cherry-pick, Clone and 27 more — each in outline and duotone at three weights, with the code for React, Vue, Svelte, Flutter and more.

30 icons · 1 of 8 groupsOpen in browser

The 30 version-control icons in Developer Tools, described

Branchbranch-git
A git branch — a line of work split off from another so changes can be made in isolation.
Cherry-pickcherry-pick
One commit lifted straight out of a row of commits — cherry-picking a single change.
Cloneclone
Clone — take a full copy of a repository, its history and all its branches.
Diffcode-diff
A code diff — what changed, line by line, compared for review.
Code reviewcode-review
Code review — somebody read the change, commented and approved it before it landed.
Conflictconflict
A merge conflict — two changes that cannot both apply to the same lines.
Diffdiff
A diff — what changed between two versions, shown as a patch to compare.
Diff filediff-file
A page marked with a plus and a minus — a diff or patch file.
Forkfork
A fork — your own copy of somebody else's repository, free to diverge.
Git bisectgit-bisect
A marker over the middle of a chain of commits — bisecting history to find the bad commit.
Git branch addgit-branch-add
A line of commits with a plus beside it — create a new branch to work on.
Git branch removegit-branch-remove
A branch with a minus beside it — delete a branch that is done with.
Commitgit-commit
A git commit — one change recorded as a snapshot with its own hash.
Git commit verticalgit-commit-vertical
A commit on a vertical line — one change in the history, drawn top to bottom.
Git comparegit-compare
Two commits with arrows between them — compare two branches or two points in history.
Git forkgit-fork
One commit splitting into two — a fork, the history going two ways from here.
Mergegit-merge
A git merge — two lines of work joined back into one branch of history.
Git merge conflictgit-merge-conflict
Two branches meeting at a cross instead of a commit — a merge that does not go through by itself.
Git pull requestgit-pull-request
A branch offered back to the line it came from — a pull request, changes proposed for review.
Git pull request closedgit-pull-request-closed
A pull request ending in a cross — closed without merging, the changes turned away.
Git pull request creategit-pull-request-create
A pull request with a plus above it — open a new pull request from this branch.
Git pull request draftgit-pull-request-draft
A pull request whose line is still dashed — a draft, not yet ready for review.
Monorepomonorepo
A monorepo — every project in one repository under a single root.
Pull requestpull-request
A pull request — asking for your branch to be reviewed and merged.
Rebaserebase
Rebase — a branch's commits replayed on top of a different base.
Repositoryrepository
A repository — where the source code lives, together with its history.
Reviewreview
Review — another pair of eyes on the change before it lands in the main branch.
Stashstash
Stash — put changes aside for now and pick them up again later.
Git tagtag-git
A git tag — a commit with a name on it, a pinned version label.
Version controlversion-control
Version control — every change kept as history, git commits you can go back to.

In code, each is one import — import { BranchGit } from "@iconmind/react/icons/branch-git" — and the same name in Vue, Svelte, Solid, Preact, React Native, Astro, Blade and Flutter.

Narrow it by tag

Every version-control icon in Developer Tools, free to ship

30 icons in outline and duotone at three weights, generated from one grid so nothing in the set can drift out of step. MIT licensed — commercial use, no attribution, no seat count.

Other groups in Developer Tools