Open cenamiller opened 1 month ago
/glade/u/home/huebler/Code/sys_admin/gitUpdateScripts/updateClubbRelease.sh
Here is Gunther's script
Testing methods for duplicating the public repo into a private one. My understanding is that we DON'T want to just create a fork. Starting here: https://docs.github.com/en/repositories/creating-and-managing-repositories/duplicating-a-repository
Created private test repo here using the above instructions: https://github.com/cenamiller/samurai_test
Looks like all branches and commit history are intact
Oops - did my test with apache license. When we do it for real as an NCAR repo, should use: [GPL-3.0 license]
Need to modify and test Gunther's syncing script, and see how the code coverage integration reacts...
Need to try to add GPU runner to cenamiller/samurai_test, the cpu cloud runners were transferred automatically. Code coverage was not transferred.
Private repo is create: github.com/NCAR/samurai-dev, all past commits/branches were mirrored.
Still working on transferring project board and issues. There will be a big announcement when we switch development work to NCAR/samurai-dev
Based on Haiying's research, we're creating a private repo that will be used for automated testing on CISL resources. Private repos can be kept more secure from malicious actors. Goal is to keep public repo open, and development happens in private repo and frequently updates the public repo.
Supreeth has brought up a concern - it can be difficult to synchronize the repos. There are scripts that can do it automatically. Need to think about it, and Sheri has offered to talk to Gunther about how he synchronizes the CLUBB repo.