Community Git Server Updates on 1 June 2023 at 1300 UTC

On 1 June 2023 at 13:00 UTC (9:00 AM EDT), access to will be disabled for approximately 1 hour. The downtime will facilitate the move of the community git repositories to a newer host server as well as the renaming of “master” branches to “main.” Once the work is complete, access will be restored and an email will be sent to indicate that it is OK to resume using

If you use the server, there are some things that you need to do after the changes are complete.

The host key identification for will change as a result of the move to a new host. In order to access the repositories with your SSH key via, remove the old SSH host identification from your known_hosts file. For OpenSSH, the following commands should work on Linux systems and on Windows in the Git Bash shell. If you use some other method to access the community git server, please consult that software’s documentation.

    ssh-keygen -R

If your known_hosts file is in a non-standard location, add it to the command line with the -f switch:

    ssh-keygen -R -f /path/to/ssh/known_hosts_file

You can fetch the new server’s keys in advance by running ssh-keyscan and appending them to your known_hosts file. Otherwise, you will be prompted to add the new server’s SSH host keys to your known_hosts file on the first fetch. The example command line below assumes that your known_hosts file is in the standard location for OpenSSH.

    ssh-keyscan -H >> ~/.ssh/known_hosts

If you manage remote mirrors of the community repositories that use git pull to stay up to date, you will likely need to make similar changes on your servers if they use to access the repositories. If your mirrors are automatically pushed to by the community server, then you should not have to do anything as a result of the host key changes.

The following repositories will have their master branch renamed to main:

  • Evergreen.git
  • Hatch.git
  • NCIPServer.git
  • OpenSRF.git
  • SIPServer.git
  • eg-antora.git
  • history.git
  • working/Evergreen.git
  • working/Hatch.git
  • working/NCIPServer.git
  • working/OpenSRF.git
  • working/SIPServer.git
  • working/eg-antora.git
  • working/random.git
  • evergreen/equinox.git
  • evergreen/joelewis.git
  • evergreen/pines.git
  • evergreen/tadl.git
  • evergreen/masslnc.git

You may run the following three commands to update your local repository from master to main.

    git fetch --all
    git checkout -b main origin/main
    git branch -d master

The above commands assume that your origin repository is one of the above, or an automated mirror of one of the above. If that is not the case, then modify the checkout command as appropriate.

Mirrors that are updated by pushes from the community server will get the new main branch pushed automatically. However, the master branches may not be deleted from these mirrors. If you have such a mirror, you should check it for the presence of the master branch and take steps to delete it if you like. All future pushes will go to the main branch.

Other mirrors will likely require updates as well. However, the possibilities are too diverse for us to provide any universal steps in this email. If you get stuck trying to update your own mirrors, then feel free to ask questions in the #evergreen channel on or to email the Evergreen development email list.