Adding a Git Baselibs Component: Difference between revisions

Updates up to the Main Repo
No edit summary
 
Line 51: Line 51:
  $ git push --tags
  $ git push --tags


=== Main Repo ===
== Main Repo ==


Don't forget to then update the .gitmodules in the main ESMA-Baselibs repo to refer to the new version/<num> branch. To do this, first do a nice clean checkout of the repo for safety:
We need to add/update the <tt>.gitmodules</tt> in the main ESMA-Baselibs repo to refer to the new version/<num> branch. To do this, first do a nice clean checkout of the repo for safety:


  $ git clone --recursive git@developer.nasa.gov:mathomp4/ESMA-Baselibs.git
  $ git clone --recursive -j 4 git@developer.nasa.gov:mathomp4/ESMA-Baselibs.git


Then, you can go into it and edit <tt>.gitmodules</tt>. Once you've changed the branch to use then issue:
Then, you can go into it and edit <tt>.gitmodules</tt>. Once you've changed the branch to use then issue:


  $ git submodule update --remote <component>
  $ git submodule add -b version/1.0.1 git@developer.nasa.gov:mathomp4/ESMA-Baselibs-gFTL.git gFTL


If you have more than one, you can leave off the component and it will update all the submodules.
This should add something to the <tt>.gitmodules</tt>