| Version 2 (modified by , 14 years ago) ( diff ) | 
|---|
Contributing to WebKit using GitHub
TODO: Add an overview for what you might want to do this.
Document status: Proposal
Setup
- Create a GitHub account (if you don't already have one)
 - Fork https://github.com/WebKit/webkit
 - $ git clone git@github.com:yourname/webkit.git
 
Writing code
- $ git checkout master -b awesomefeature
 - Write some awesome code.
 - Commit locally and push to origin (your GitHub account) as you normally would with git.
 
Tracking upstream
- One-time setup: $ git remote add upstream git://github.com/WebKit/webkit.git
 - $ git fetch upstream
 - $ git merge upstream/master
 - $ git push origin master
 
If you never modify your local master branch, merging upstream/master will always be a fast-forward merge (i.e., no merge conflicts). You can then merge these new commits into your in-flight feature branches as you normally would with git.
Getting your code reviewed
- Find a reviewer who is interested in reviewing your awesome feature.
 - Create a pull request by going to https://github.com/yourname/webkit/pull/new/awesomefeature
 - Click the "Change Commits" button to select that reviewer's base branch of WebKit. TODO: Investigate whether we can make reviewers members of the "WebKit" organization so you can just use WebKit/webkit@master as the base branch.
 - Write a helpful description of your pull request and click "Send pull request".
 - Iterate with the reviewer as usual using GitHub's review tools.
 
Accepting a pull request
  Note:
 See   TracWiki
 for help on using the wiki.