In the spirit of open source software development, jQuery always encourages community code contribution. To help you get started and before you jump into writing code, be sure to read these important contribution guidelines thoroughly:
If you encounter a bug in the framework you can report it on the issue tracker here on Github. Questions about how to use the framework or problems with your custom code can be posted on the forum. The jQuery Mobile API Documentation, ThemeRoller and Download Builder have their own repo where you can report issues.
Before opening a new issue please check if the same or a similar issue already has been reported. Tip: Besides the search tool of the issue tracker you can filter issues by label.
When submitting an issue include the following:
- Issue description
- Test page (see below)
- Steps to reproduce
- Expected outcome
- Actual outcome
- Platforms/browsers (including version) and devices tested
- jQuery Mobile and jQuery core version used
- Other relevant information, e.g. using PhoneGap
It is IMPORTANT that you always provide a test page when submitting an issue!
Why? - This ensures that we are looking at exactly the same thing when testing on our devices and that we know about all markup and code that is in play.
What? - Keep the test page as simple as possible. Only include markup/code that is required to reproduce the issue.
- You will notice if the issue has been fixed already
- It enables us to edit your code if necessary
- The test page won't disappear or change while we are looking into the issue
- We can test again after committing a fix for the issue
JS Bin instructions: When you start editing the JS Bin, the url will update and contain a new version number. As long as you keep the JS Bin open in your browser this url won't change. Copy the url in your issue report when you are done editing. If your test case requires multiple "single" jQuery Mobile pages, open the JS Bin on multiple tabs on your browser and each of them will get an unique url. Link to this url without "/edit" at the end on your other page(s).
If you have an idea for a new feature or a suggestion how to improve an existing feature, let us know!
Please note that we will flag the issue as feature request and then close it. We check requests on regular base and when we decide to implement a feature we set a milestone and re-open the ticket.
When submitting a pull request for review there are a few important steps you can take to ensure that it gets reviewed quickly and increase the chances that it will be merged (in order of descending importance):
- Include tests (see Testing)
- Follow the jQuery Core style guide
- Limit the scope to one Issue/Feature
- Small focused commits, ideally less than 10 to 20 lines
- Avoid merge commits (see Pro Git's chapter on rebasing, section Rebasing below)
- Add the appropriate commit message (see below)
Taken together, the above reduces the effort that's required of the contributor reviewing your pull request.
Commit messages should include four components:
- The WHERE - a single word that categorizes and provides context for the commit and its message, followed by a colon (:). This is typically the name of the plugin being worked on, but sometimes might be something like Build: or Docs:
- The WHAT - a sufficient summary of the fix or change made (example: modified the foo to no longer bar), followed by a period (.)
- The WHY #Num - the ticket number with a #sign so Trac creates a hyperlink (example: #1234), followed by a hyphen/dash (-)
- The WHY Name - the name of the ticket. Notice this is different than summary of the fix. This is a short description of the issue (example: dialog: IE6 crashed when foo is set to bar)
Combined into one, here's a full example:
"Dialog: modified the foo to no longer bar. Fixed #1234 - dialog: IE6 crashed when foo is set to bar" \WHERE/:\------------- WHAT -------------/.\ WHY #Num /-\---------------- WHY Name ----------------/
Often times when working on a feature or bug fix branch it's useful to pull in the latest from the parent branch. If you're doing this before submitting a pull request it's best to use git's rebase to apply your commits onto the latest from the parent branch. For example, working on
new-feature branch where
upstream is the remote at
git checkout new-feature git pull --rebase upstream master ## ... here you may have to resolve some conflicts ... ##
You can now push to your own fork and submit the pull request. Keep in mind that it's only a good idea to do this if you haven't already submitted a pull request unless you want to create a new one because your origin remote (your fork) will report a discrepancy. Again, please refer to the chapter in Pro Git on rebasing if you're new to it.
Thank you for contributing to the jQuery Mobile project!