Renaming The Default Branch

Runtimes C++
21

Hi Anton,

22

Phabricator was still watching master.
It should still have been autoclosing I guess, with some extra latency based on the mirroring.

I’ve switched the primary branch from master->main in phabricator (just now), so it should be faster for future commits.

23

…and your review still hasn’t been autoclosed, and probably won’t be. But new ones are working now. Sorry for the glitch and thanks for reporting it!

(I suspect a phab bug where if it’s seen a commit on a non-primary branch, maybe it won’t process that same commit again if it shows up on the primary branch.)

24

Nice!

One issue that I noticed is that it seems all commit emails now go to
the llvm-branch-commits mailing list. For example,
http://lists.llvm.org/pipermail/llvm-branch-commits/2020-December/015623.html
was pushed to 'main', but still went to this list which is supposed to
be for commits to release branches and such.

Is there some way that can be fixed?

Thanks,
Hans

25

Hi,
Currently there are two issues I would like to address:

  1. While we understand new commits to the ‘main’ branch are somewhat slow to synchronize (about 5 minutes) to the old ‘master’ branch, we are not planning to address the issue at this time. Developers will notice an immediate improvement by migrating their workflows to the new ‘main’ branch. We advise everyone to stop relying on ‘master’ and migrate to the ‘main’ branch as soon as possible.

  2. As Hans just pointed out, the automation we have in place to make commits post to the mailing lists is not working correctly. I will be looking into this today and hope to have it resolved soon.

-Mike

26

Hi,
Currently there are two issues I would like to address:

  1. While we understand new commits to the ‘main’ branch are somewhat slow to synchronize (about 5 minutes) to the old ‘master’ branch, we are not planning to address the issue at this time. Developers will notice an immediate improvement by migrating their workflows to the new ‘main’ branch. We advise everyone to stop relying on ‘master’ and migrate to the ‘main’ branch as soon as possible.

When will it be correct to push to main for all of the repos under the GitHub org?

27

Hi,
Currently there are two issues I would like to address:

  1. While we understand new commits to the ‘main’ branch are somewhat slow to synchronize (about 5 minutes) to the old ‘master’ branch, we are not planning to address the issue at this time. Developers will notice an immediate improvement by migrating their workflows to the new ‘main’ branch. We advise everyone to stop relying on ‘master’ and migrate to the ‘main’ branch as soon as possible.

When will it be correct to push to main for all of the repos under the GitHub org?

Hi Hubert,
I do not have a specific timeline defined as of yet. My hope is to get all of the other projects under the llvm org migrated to using a ‘main’ branch by default prior to the end of January 2021. I do not control all of the other repositories though, so I will be working with their owners to accomplish this according to a schedule which will cause the least disruption to the individual projects.

Thanks,
Mike

28

I just updated the MLIR website repo: https://github.com/llvm/mlir-www/

29

Hi,

I'm noticing some issues using arcanist to land patches now that we've
migrated to using main instead of master.

Using `arc land` It seems to be trying to fetch and squash changes from
master instead of main.

Using `arc land hold`, It says to push the changes use ` $ git push --
origin 0956df44acc3:refs/heads/master`
Again refering to master instead of main.

Trying to push to main manually often seems to result in conflicts and
the push not suceeding.

~Nathan

30

I noticed the other repositories such as
https://github.com/llvm/llvm-zorg,
GitHub - llvm/llvm-test-suite,
https://github.com/llvm/llvm-www have not followed this change. Have
these been forgotten?

Michael