Difference between revisions of "Projects/rekonq/Git with rekonq HowTo"

Jump to: navigation, search
(Created page with '=Introduction= This is a tutorial on how we use git for rekonq development, it's not meant to be a Git manual. For information on how git is used an manage inside KDE look [htt...')
 
(Introduction)
Line 1: Line 1:
 
=Introduction=
 
=Introduction=
  
This is a tutorial on how we use git for rekonq development, it's not meant to be a Git manual.
+
This is a tutorial on how we use git for rekonq development, it's not meant to be a git manual.
  
 
For information on how git is used an manage inside KDE look [http://community.kde.org/Sysadmin/GitKdeOrgManual here].
 
For information on how git is used an manage inside KDE look [http://community.kde.org/Sysadmin/GitKdeOrgManual here].

Revision as of 11:16, 16 January 2011

Introduction

This is a tutorial on how we use git for rekonq development, it's not meant to be a git manual.

For information on how git is used an manage inside KDE look here.

Note: In other to used ReviewBoard you need an KDE identity account.

Git for frequent contributions (or patches with more than one commit)

Frequent contributors should have their own repository clone. KDE developers have git.kde.org available and services such as Gitorious can be used by the rest.

This should be the place were all the work is uploaded, and there should be a new branch for every new feature. Once a feature is ready for revision, you should upload a diff to ReviewBoard and indicate the repository and branch where the feature can be found. This way anyone wanting to test it can simply add a new remote. Once the feature is ready for shipping, you're allowed to push it to the main repository if you have access or you can ask someone to do it for you if you don't. Please rebase the branch beforehand when possible.

Git for one-time simple patches

Simple patches may be uploaded directly to ReviewBoard for revision. A rekonq developer will commit it when necessary.

Note for commiters: When commiting a patch from reviewboard use the --author option to credit the author.

This workflow takes more time to test because testers have to download the diff and apply it manually, so it's only recommended for people that contribute a casual patch and don't plan on working on rekonq in the future.


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal