Git: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 7: | Line 7: | ||
[https://github.com/KFTrack/BTrk BTrk github repo] | [https://github.com/KFTrack/BTrk BTrk github repo] | ||
==Quick Start== | |||
Please also see the basic [[CodeRecipe|code recipe]] for an introduction to setting up the environment, checking out code and building. | |||
If you are going to commit anything, you must understand and follow the [https://cdcvs.fnal.gov/redmine/projects/mu2eofflinesoftwaremu2eoffline/wiki/Git_Workflow_for_Mu2e detailed mu2e instructions] | |||
<font>need to add instructions on first-time use: ~.gitconfig</font> | |||
* checkout the main repository | |||
** readonly: <pre>git clone http://cdcvs.fnal.gov/projects/mu2eofflinesoftwaremu2eoffline/Offline.git</pre> | |||
** with kerberos authentication for committing code <pre>git clone ssh://p-mu2eofflinesoftwaremu2eoffline@cdcvs.fnal.gov/cvs/projects/mu2eofflinesoftwaremu2eoffline/Offline.git</pre> | |||
* checkout the head to a local working branch (recommended) | |||
<pre>get checkout -b work</pre> | |||
* see the history of a file | |||
<pre>git log fileSpec</pre> | |||
* list tags | |||
<pre>git tag -l</pre> | |||
* checkout a tag or branch into the working area | |||
<pre>get checkout tagOrBranchName </pre> | |||
* update the local repository | |||
<pre>git fetch</pre> | |||
* update the local repository and checkout the head into the working area | |||
<pre>git pull</pre> | |||
* see what the status is | |||
<pre>git status</pre> | |||
Please see the references or many web resources for details on git commands and features. | |||
If you are going to commit anything, you must understand and follow the [https://cdcvs.fnal.gov/redmine/projects/mu2eofflinesoftwaremu2eoffline/wiki/Git_Workflow_for_Mu2e detailed mu2e instructions] | |||
==References== | ==References== |
Revision as of 21:42, 17 February 2017
Introduction
The primary source code management system for the Mu2e Offline software is a git that is hosted on the Fermilab redmine site. Other Mu2e software is managed using other source code management systems.
Please follow these instructions for the mu2e conventions on commits.
Quick Start
Please also see the basic code recipe for an introduction to setting up the environment, checking out code and building.
If you are going to commit anything, you must understand and follow the detailed mu2e instructions
need to add instructions on first-time use: ~.gitconfig
- checkout the main repository
- readonly:
git clone http://cdcvs.fnal.gov/projects/mu2eofflinesoftwaremu2eoffline/Offline.git
- with kerberos authentication for committing code
git clone ssh://p-mu2eofflinesoftwaremu2eoffline@cdcvs.fnal.gov/cvs/projects/mu2eofflinesoftwaremu2eoffline/Offline.git
- readonly:
- checkout the head to a local working branch (recommended)
get checkout -b work
- see the history of a file
git log fileSpec
- list tags
git tag -l
- checkout a tag or branch into the working area
get checkout tagOrBranchName
- update the local repository
git fetch
- update the local repository and checkout the head into the working area
git pull
- see what the status is
git status
Please see the references or many web resources for details on git commands and features. If you are going to commit anything, you must understand and follow the detailed mu2e instructions
References
- mu2e git instructions
- git home Documentation reference
- redmine repository browser
- Fermilab redmine
- talk at the Software and Simulation Meeting, Sept 17, 2014.
- Marc P's suggested git workflow for simple git projects
- Fermilab git workshop and related materials
- managing and creating new redmine repositories