
Recent events have brought to light the negative connotations of having the main branch on a repository called `master`. Whether you want to change your primary branch name for this reason or just for fun, it is important to know how to do so and there are a few key steps to ensure that the change goes smoothly.

## Changing Future Repositories

Before we jump into changing our existing repos, let's make sure that we avoid the issue altogether in our future projects. In GitHub, under `Settings > Repositories` there is an option to name your default branch for future projects. Remember, this changes it for your personal account, but you can do the same for an organization.

As a note, on October 1st of this year, GitHub will be setting the default branch for new repositories to `main`.

## Updating Existing Repos

Now, to change an existing repo to a new name add a new branch from the existing `master`, which we will call `main` for this example. With an exact copy now on `main` go to the repository `Settings > Branches` and change the default branch to `main`. Then we can delete the `master` branch, which will alert us that the open pull requests for `master` will be affected. You can use a tool, like [this one from Edward Thomson](https://github.com/ethomson/retarget_prs), to re-target the pull requests to the new branch.

And that's it! You've made the change away from the `master` branch. If you still think it sounds a bit too complicated or too much work, GitHub announced that it will be releasing a feature to make a seamless transition when renaming the default branch by the end of the year.

## Credit

Today's Tuesday Tips was adapted from [a post on the DEV Community](https://dev.to/tracycss/renaming-your-master-branch-to-main-in-github-24cm).


<p>Recent events have brought to light the negative connotations of having the main branch on a repository called <code>master</code>. Whether you want to change your primary branch name for this reason or just for fun, it is important to know how to do so and there are a few key steps to ensure that the change goes smoothly.</p>

<h2>Changing Future Repositories</h2>

<p>Before we jump into changing our existing repos, let&#39;s make sure that we avoid the issue altogether in our future projects. In GitHub, under <code>Settings &gt; Repositories</code> there is an option to name your default branch for future projects. Remember, this changes it for your personal account, but you can do the same for an organization.</p>

<p>As a note, on October 1st of this year, GitHub will be setting the default branch for new repositories to <code>main</code>.</p>

<h2>Updating Existing Repos</h2>

<p>Now, to change an existing repo to a new name add a new branch from the existing <code>master</code>, which we will call <code>main</code> for this example. With an exact copy now on <code>main</code> go to the repository <code>Settings &gt; Branches</code> and change the default branch to <code>main</code>. Then we can delete the <code>master</code> branch, which will alert us that the open pull requests for <code>master</code> will be affected. You can use a tool, like <a href="https://github.com/ethomson/retarget_prs">this one from Edward Thomson</a>, to re-target the pull requests to the new branch.</p>

<p>And that&#39;s it! You&#39;ve made the change away from the <code>master</code> branch. If you still think it sounds a bit too complicated or too much work, GitHub announced that it will be releasing a feature to make a seamless transition when renaming the default branch by the end of the year.</p>

<h2>Credit</h2>

<p>Today&#39;s Tuesday Tips was adapted from <a href="https://dev.to/tracycss/renaming-your-master-branch-to-main-in-github-24cm">a post on the DEV Community</a>.</p>

Assets

Square

How to Rename Your Master Branch on GitHub

View post on our website

Tall

How to Rename Your Master Branch on GitHub

View post on our website

Wide

How to Rename Your Master Branch on GitHub

View post on our website

Other

How to Rename Your Master Branch on GitHub