forked from hafs-community/HAFS
-
Notifications
You must be signed in to change notification settings - Fork 0
Quick start guide for HAFS developer v2.0
Jili Dong edited this page Mar 5, 2020
·
10 revisions
This is a quick guide for developers to update HAFS code and fix bugs. Currently the guide is on working on hafs-community repository directly instead of requiring developers to create a new individual fork.
% git clone https://github.com/hafs-community/HAFS.git
$ cd HAFS
$ git checkout develop
$ git submodule update --init --recursive
Find out the submodule(s) the user would like to work on; please refer to Hierarchical Repository Structure
Now use FV3 (fv3atm) as an example:
$ cd HAFS/sorc/hafs_forecast.fd/FV3
$ git checkout support/HAFS
$ git pull origin support/HAFS
$ git checkout -b feature/change_sth
Work on this new branch by modifying/adding code
When ready to push the update/bug-fix/changes, first sync with the support/HAFS branch:
$ git checkout support/HAFS
$ git pull origin support/HAFS
$ git checkout feature/change_sth
$ git merge support/HAFS
Now commit and push the changes
$ git add modified-files
$ git commit -m "update message"
$ git push origin feature/change_sth
Now it is time to do a pull request (PR) on github.com
Please request merging hafs-community/feature/change_sth to hafs-community/support/HAFS through creating a pull request