# \#git

**URL:** https://discourse.itk.org/tag/git/71.md

[Latest](https://discourse.itk.org/latest.md) · [Categories](https://discourse.itk.org/categories.md) · [Tags](https://discourse.itk.org/tags.md)

---

## [ITK Git repository primary branch name transition from master to main](https://discourse.itk.org/t/itk-git-repository-primary-branch-name-transition-from-master-to-main/7569)

<div class="topic-metadata">

**Author:** [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)\
**Replies:** 5\
**Last updated:** [July 4, 2025, 9:27am UTC](https://discourse.itk.org/t/itk-git-repository-primary-branch-name-transition-from-master-to-main/7569 "2025-07-04T09:27:06Z")

</div>

Hi folks, ITK’s default, primary branch name has been renamed from master to main. New GitHub clones will default to this branch. A few notes on changes that might be required. GitHub Forks When you visit your fork o…

---

## [Tip of the day: How to sync your pull request branch with the master branch](https://discourse.itk.org/t/tip-of-the-day-how-to-sync-your-pull-request-branch-with-the-master-branch/6491)

<div class="topic-metadata">

**Author:** [@Niels\_Dekker](https://discourse.itk.org/u/Niels_Dekker)\
**Replies:** 3\
**Last updated:** [March 5, 2024, 2:09pm UTC](https://discourse.itk.org/t/tip-of-the-day-how-to-sync-your-pull-request-branch-with-the-master-branch/6491 "2024-03-05T14:09:05Z")

</div>

Before pushing a local branch, it’s usually recommended to synchronize the branch with the latest revision of the main branch (the master branch, in the ITK git). While working on my local feature-branch, I often found m…

---

## [Unable to commit to forked ITK repo on github](https://discourse.itk.org/t/unable-to-commit-to-forked-itk-repo-on-github/1611)

<div class="topic-metadata">

**Author:** [@Gordian](https://discourse.itk.org/u/Gordian)\
**Replies:** 3\
**Last updated:** [February 20, 2019, 1:45pm UTC](https://discourse.itk.org/t/unable-to-commit-to-forked-itk-repo-on-github/1611 "2019-02-20T13:45:51Z")

</div>

Hello, i have trouble to commit to my fork of the ITK. I would like to try and share my changes in my local group before making a pull request. I forked the ITK repo and cloned the fork to have a local copy. Afterwards…

---

## [Check out open gerrit topics](https://discourse.itk.org/t/check-out-open-gerrit-topics/1597)

<div class="topic-metadata">

**Author:** [@jhlegarreta](https://discourse.itk.org/u/jhlegarreta)\
**Replies:** 4\
**Last updated:** [February 14, 2019, 4:04am UTC](https://discourse.itk.org/t/check-out-open-gerrit-topics/1597 "2019-02-14T04:04:31Z")

</div>

Folks, is there a way to checkout open gerrit topics that were not transitioned to GitHub? I’d like to finish work that I left behind a while ago. Since gerrit was put to read-only mode, searches by keywords cannot be…

---

## [ITK Development Git Cheatsheet / Quick Reference PDF](https://discourse.itk.org/t/itk-development-git-cheatsheet-quick-reference-pdf/1398)

<div class="topic-metadata">

**Author:** [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)\
**Replies:** 0\
**Last updated:** [November 6, 2018, 3:49pm UTC](https://discourse.itk.org/t/itk-development-git-cheatsheet-quick-reference-pdf/1398 "2018-11-06T15:49:16Z")

</div>

In addition to our CONTRIBUTING.md documentation, and the Software Process section of the ITK Software Guide, we have an ITK development quick reference PDF: This has been updated for contribution on GitHub. :octopus: …

---

## [release-4.13 branch for ITK 4 bugfix patches](https://discourse.itk.org/t/release-4-13-branch-for-itk-4-bugfix-patches/1166)

<div class="topic-metadata">

**Author:** [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)\
**Replies:** 0\
**Last updated:** [July 31, 2018, 2:48am UTC](https://discourse.itk.org/t/release-4-13-branch-for-itk-4-bugfix-patches/1166 "2018-07-31T02:48:34Z")

</div>

Hi folks, We now have a release-4.13 maintenance Git branch for ITK 4. Soon, the release branch will point to ITK 5. While we will be focusing our efforts on ITK 5, critical bugfixes can be merged into the release-4.…
