You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On May 31 2025 at approximately 17:00 UTC, the default branch for the git-bug repository will be changed from master to trunk.
Why is this being done?
The current default branch name is outdated and has negative connotations.
Why "trunk"?
trunk has history -- it is the traditional name for the primary development line in other version control systems like Subversion and CVS. It also aligns well with git's metaphors for "branches" and "trees" -- trunk feels semantically aligned and descriptive of it being the primary/core development line.
It also helps to emphasize a trunk-based development workflow, where branches are short-lived and the aim is to commit to trunk frequently.
What actions do I need to take?
If you have cloned this repository, you'll need to take a few actions in your local copy in order to change the default branch.
1. Rename your local default branch
git branch -m master trunk
2. Set the new default for origin/HEAD
git remote set-head origin trunk
NOTE
If you have a different remote name for this git repository, be sure to reference that instead of origin.
3. Update any scripts or references to the old default branch
Be sure to update any scripts, packages, or other references to the old default branch name.
You can safely perform these migrations today. trunk will be kept up-to-date with the current default tree automatically.
The text was updated successfully, but these errors were encountered:
This change introduces a pipeline job called `mirror` that will push to
`refs/heads/trunk` automatically, in order to keep it in sync with the
default tree.
This job is restricted to the SoT for git-bug, and will only execute for
the first run of the workflow.
Refs: #1404
Change-Id: If65f83ce9058dd01aa74f6841dc58ac040284b18
This change introduces a pipeline job called `mirror` that will push to
`refs/heads/trunk` automatically, in order to keep it in sync with the
default tree.
This job is restricted to the SoT for git-bug, and will only execute for
the first run of the workflow.
Refs: #1404
Change-Id: If65f83ce9058dd01aa74f6841dc58ac040284b18
This change introduces a pipeline job called `mirror` that will push to
`refs/heads/trunk` automatically, in order to keep it in sync with the
default tree.
This job is restricted to the SoT for git-bug, and will only execute for
the first run of the workflow.
Refs: #1404
Change-Id: If65f83ce9058dd01aa74f6841dc58ac040284b18
On
May 31 2025
at approximately17:00 UTC
, the default branch for thegit-bug
repository will be changed frommaster
totrunk
.Why is this being done?
The current default branch name is outdated and has negative connotations.
Why "trunk"?
trunk
has history -- it is the traditional name for the primary development line in other version control systems like Subversion and CVS. It also aligns well with git's metaphors for "branches" and "trees" --trunk
feels semantically aligned and descriptive of it being the primary/core development line.It also helps to emphasize a trunk-based development workflow, where branches are short-lived and the aim is to commit to trunk frequently.
What actions do I need to take?
If you have cloned this repository, you'll need to take a few actions in your local copy in order to change the default branch.
1. Rename your local default branch
2. Set the new default for
origin/HEAD
3. Update any scripts or references to the old default branch
Be sure to update any scripts, packages, or other references to the old default branch name.
You can safely perform these migrations today.
trunk
will be kept up-to-date with the current default tree automatically.The text was updated successfully, but these errors were encountered: