Archive:Development/Tutorials/Git/Pushing: Difference between revisions
(Write section explaining how to push directly) |
m (oops, looks like I've been using too much github) |
||
| Line 20: | Line 20: | ||
If you cloned a git:// repo originally, you won't be able to push to it. You can add another remote by running: | If you cloned a git:// repo originally, you won't be able to push to it. You can add another remote by running: | ||
<code>git remote add origin-rw git@ | <code>git remote add origin-rw git@gitorious.org:...</code> | ||
Where origin-rw is whatever name you want to call it, and you use the actual path to the remote, not the placeholder. | Where origin-rw is whatever name you want to call it, and you use the actual path to the remote, not the placeholder. | ||
Then you too can push: | Then you too can push: | ||
<code>git push origin-rw master</code> | <code>git push origin-rw master</code> | ||
Revision as of 22:55, 16 December 2009
TODO:
- Show how to do both pushing and merge requesting.
Getting an account on Gitorious
Since nearly all of KDE's git repositories are hosted on gitorious, this is rather important. Fortunately, this part is relatively easy:
- Go to http://gitorious.org/ and follow the link to register.
- Fill out the form.
Deciding whether to push directly or make a merge request
There are two basic ways to get code into KDE's project repositories: you can push it there yourself or make a merge request to have someone else do it for you. While that might make merge requests seem pointless, there are some reasons where you will want to use merge requests instead of direct pushes:
- Code review: Having your code looked at by another person (one who knows the project code better maybe) can be useful to keep easily preventable mistakes from entering the repository.
- First time commits: The first time you write code for a project, it is polite to use a merge request instead of pushing the code directly. This is a good way to make sure that you are on the same page as the other developers (and the maintainers) of the project which you are working on.
- Non-KDE developers: If you aren't a KDE deveoper (eg. you aren't in the kde-developers group on gitorious), and you want to get a quick fix included in a KDE program, a merge request is a simple way to get this done, since you do not have the ability to push directly. If you find yourself doing this frequently, you might want to consider "making it official" and applying to be a KDE Developer, it isn't that difficult to do.
Pushing directly
Pushing in git is the act of adding commits from your local repository to a remote one. It's only possible to write to git remotes which are writable. In the KDE/Gitorious setups, the git://gitorious.org/... remotes are read only, while the SSH ([email protected]:...) ones are readable and writable.
Whatever remote repository you cloned originally is named by default "origin". So if you wanted to push the contents of the current branch to origin's master branch, you would be able to simply run:
git push origin master
If you cloned a git:// repo originally, you won't be able to push to it. You can add another remote by running:
git remote add origin-rw [email protected]:...
Where origin-rw is whatever name you want to call it, and you use the actual path to the remote, not the placeholder.
Then you too can push:
git push origin-rw master