Transitioning from Vlab

This page is focused on issues and procedures that are specific to developers who previously used the code now in ufs-s2s-model when it was in the Vlab (Virtual Lab) development and collaboration environment.

About the Transition

The ufs-s2s-model was moved from the Vlab gerrit EMC_FV3-MOM6-CICE repository to this GitHub repository on Nov 13, 2019. The development activities on the Vlab repository have been suspended since then, and all developers are expected to move their work to this GitHub repository.

Transitioning Branches from Gerrit to GitHub

This section is for developers that would like to transition their EMC_FV3-MOM6-CICE5 branches to GitHub.

The ufs-s2s-model repository follows the forking workflow. A develop branch is used to integrate all the development work (equivalent to the master branch in Vlab). Besides that only production and release branches will be maintained in the repository. All the development work will be at developers' personal forks and pull requests need to be made to commit the code changes into the authoritative ufs-s2s-model repository.

No personal branches in EMC_FV3-MOM6-CICE5 Vlab repository have been moved to GitHub. If developers want to continue their development work and commit code to the ufs-s2s-model authoritative GitHub repository, they need to transition their EMC_FV3-MOM6-CICE5 branches to their personal fork of the ufs-s2s-model on GitHub. If a branch of any component (eg, fv3atm) is associated with the EMC_FV3-MOM6-CICE5 branch being moved to GitHub, the developer will also need to fork that component's repository and re-create the component branch on GitHub.

General helpful information about Working with Forks

1. To fork the ufs-s2s-model, login to GitHub using a personal account (e.g.: FirstLast-NOAA). Then go to: https://github.com/ufs-community/ufs-s2s-model, click on the "fork" button. If it asks for a GitHub account, choose the developer’s personal account. If a component branch (e.g.: fv3atm) is associated with the EMC_FV3-MOM6-CICE5 branch, please go to: https://github.com/NOAA-EMC/fv3atm, click on the “fork” button to make a personal fork for fv3atm repository. Repeat as necessary for any component with a Vlab branch.

2. To move a component branch from Vlab to your GitHub fork of the component:

% git clone https://github.com/FirstLast-NOAA/fv3atm.git
% cd fv3atm
% git remote add VL gerrit:FV3
% git fetch VL
% git checkout VL/fv3atm_branch_name
% git checkout -b fv3atm_branch_name
% git push --set-upstream origin fv3atm_branch_name

Your component fork should now have a branch equivalent to your Vlab branch.