forked from cms-sw/cmssw
-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Santiago Folgueras edited this page Jul 18, 2019
·
9 revisions
Use this if you don’t want to do any development but to test the code or plug your analyzer on top of it:
cmsrel CMSSW_10_6_1_patch2
cd CMSSW_10_6_1_patch2/src
cmsenv
git cms-init
git remote add dtp2-tpg-am [email protected]:dtp2-tpg-am/cmssw.git
git cms-merge-topic -u dtp2-tpg-am:v1.1_AM_106X
An organization has been created in github to allow for parallel developments by different people, we should try to follow this protocol:
- Do not push commit directly into the development branch (AM_106X_dev).
- To develop the code / add a new feature, you can use a fork of the repository and then create a PR or you could create a different branch, push it to the organization and then create a PR to the development branch.
cmsrel CMSSW_10_6_1_patch2
cd CMSSW_10_6_1_patch2/src
cmsenv
git cms-init
git remote add dtp2-tpg-am [email protected]:dtp2-tpg-am/cmssw.git
git fetch dtp2-tpg-am
git checkout AM_106X_dev
git cms-addpkg L1Trigger/DTPhase2Trigger
git cms-addpkg DataFormats/L1DTTrackFinder
git cms-addpkg Phase2L1Trigger/CalibratedDigis
git checkout -b your-branch-name
git add files-that-changed
git commit -m "write something there"
git push dtp2-tpg-am your-branch-name