12,301
edits
no edit summary
(add categories) |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 37: | Line 37: | ||
or to add all: | or to add all: | ||
<source lang="bash">git add | <source lang="bash">git add .</source> | ||
| Line 47: | Line 47: | ||
At this point, your commit is only local! You can commit as few or as many changes as you like. But at the end of the day, you should push your changes to the server: | At this point, your commit is only local! You can commit as few or as many changes as you like. But at the end of the day, you should push your changes to the server: | ||
<source lang="bash">git push origin | <source lang="bash">git push origin main</source> | ||
| Line 84: | Line 84: | ||
* git != github.com | * git != github.com | ||
** git is a local version control software. You have to install git locally on your machine | ** git is a local version control software. You have to install git locally on your machine | ||
** then (!) you can (!) add remote git servers to your local repository. This is where github, gutbucket & co (or your own git-server) come into the game | ** then (!) you can (!) add remote git servers to your local repository. This is where github, gitlab, gutbucket & co (or your own git-server) come into the game | ||
** but then again, git works fine just locally. You do not need to use a remote server, nor do you have to use github or any other service provider. | ** but then again, git works fine just locally. You do not need to use a remote server, nor do you have to use github or any other service provider. | ||
* the most important commands you want to remember are | * the most important commands you want to remember are | ||
| Line 100: | Line 100: | ||
** In fact, commit after every small step and try to be as accurate as possible on your commit messages. | ** In fact, commit after every small step and try to be as accurate as possible on your commit messages. | ||
* Branch! | * Branch! | ||
** Whenever you want to try something or are faced with the need to add, change or delete more than one or two files: create a new branch. It's easy, lightweight and you can revert or merge at any point. | ** Whenever you want to try something or are faced with the need to add, change or delete more than one or two files: create a new branch. It's easy, lightweight and you can revert or merge at any point. | ||
== Tutorial == | == Tutorial == | ||
| Line 111: | Line 111: | ||
* [http://gitref.org gitref.org] – Git Reference | * [http://gitref.org gitref.org] – Git Reference | ||
* [http://git.or.cz/course/svn.html gir.or.cz Crash Course] about git | * [http://git.or.cz/course/svn.html gir.or.cz Crash Course] about git | ||
* [https://github.com GitHub.com] | * [https://github.com GitHub] | ||
* [https://gitlab.com gitlab] | |||
* [https://bitbucket.org Bitbucket.org] (Also works with Mercurial) | * [https://bitbucket.org Bitbucket.org] (Also works with Mercurial) | ||
* [http://pcottle.github.io/learnGitBranching Learn Git branching] – nice interactive branching tutorial | * [http://pcottle.github.io/learnGitBranching Learn Git branching] – nice interactive branching tutorial | ||