Github

SCEC makes use of github, a cloud-based git repo, to archive our source code.

GIt Principles Used by SCEC

• The Master branch is deployable

We may update the master branch, but it is always considered deployable. Any significant changes should be done on a dev branch.

Example commands

maechlin CSEP1-DataModeling$ git commit -m "etl scripts"
[pm/etl 9b4209e] etl scripts
 3 files changed, 93 insertions(+)
 create mode 100644 csep_db_etl.py
 create mode 100644 csep_db_test_data.cfg
maechlin CSEP1-DataModeling$ git status
On branch pm/etl
nothing to commit, working directory clean
maechlin CSEP1-DataModeling$ git status
On branch pm/etl
nothing to commit, working directory clean
maechlin CSEP1-DataModeling$ git remote -v
origin	https://github.com/wsavran/CSEP1-DataModeling (fetch)
origin	https://github.com/wsavran/CSEP1-DataModeling (push)
maechlin CSEP1-DataModeling$ git push -u origin pm/etl
Counting objects: 5, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 1.27 KiB | 0 bytes/s, done.
Total 5 (delta 1), reused 0 (delta 0)
remote: Resolving deltas: 100% (1/1), completed with 1 local object.
To https://github.com/wsavran/CSEP1-DataModeling
 * [new branch]      pm/etl -> pm/etl
Branch pm/etl set up to track remote branch pm/etl from origin.

See Also

• CME_Project
• UCVM
• Broadband Platform
• CyberShake