services:rcs:start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
services:rcs:start [2014/12/12 11:03] – glaubitz | services:rcs:start [2014/12/12 13:19] – glaubitz | ||
---|---|---|---|
Line 26: | Line 26: | ||
{{: | {{: | ||
+ | |||
+ | To commit the changes, type //git commit -m " | ||
+ | |||
+ | **Note**: Unlike //cvs// or //svn//, anything that has been committed is not automatically pushed to the remote repository on the server (in this case, the repository in the grouphome folder). To push the changes to the remote repository, we use the command //git push//, see below. | ||
{{: | {{: | ||
+ | |||
+ | Before we push the changes to the remote repository, we can verify the changes using the command //git log// (here piped to the command //cat// to avoid displaying the git log in the //less// pager). | ||
{{: | {{: | ||
+ | |||
+ | To push the changes to the server, we use //git push//. The //push// command requires information about the remote repository to be used (called //origin// by default) as well as the development branch to be pushed to the server (//master// by default if you didn't specify any additional branches). | ||
+ | |||
+ | //git remote// lists the remote repositories that are currently available (additional can be defined using //git remote add//) while //git branch -a// lists the available branches. | ||
+ | |||
+ | Thus, in this case we need to run //git push origin master// to push our changes to the repository in the grouphome folder: | ||
{{: | {{: |
services/rcs/start.txt · Last modified: 2014/12/15 09:09 by behrmj87