Skip to content

ACTION REQUIRED: Default branch name change #1404

Closed

Description

@sudoforge

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.


Tip

You can safely perform these migrations today. trunk will be kept up-to-date with the current default tree automatically.


The change will be made automatically by a scheduled task. The scheduled task will merge #1464, which updates the trunk pipeline to:

  • Run for the trunk branch, and
  • Invert the mirror pipeline to push to refs/heads/master

The refs/heads/trunk -> refs/heads/master sync will be kept in place until January 31 2026 to support downstream package maintainers and users who have scripts or packages that build from source and hardcode refs/heads/master.

Activity

  1. pinned this issue on May 9, 2025
  2. added 5 commits that reference this issue on May 21, 2025
    4c3c54d
    0b52ea9
    ca40c0f
    ddca663
    01d6899
  3. added a commit that references this issue on Jun 7, 2025
    555fc2d
  4. unpinned this issue on Aug 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/meta/configRelates to repository configurationkind/featureRelates to a new feature

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions