build | ||
demos | ||
external | ||
tests | ||
themes/base | ||
ui | ||
.editorconfig | ||
.gitignore | ||
.jshintrc | ||
AUTHORS.txt | ||
GPL-LICENSE.txt | ||
grunt.js | ||
jquery-1.7.2.js | ||
MIT-LICENSE.txt | ||
package.json | ||
README.md |
jQuery UI - Interactions and Widgets for the web
jQuery UI provides interactions like Drag and Drop and widgets like Autocomplete, Tabs and Slider and makes these as easy to use as jQuery itself.
If you want to use jQuery UI, go to jqueryui.com to get started. Or visit the Using jQuery UI Forum for discussions and questions.
If you are interested in helping develop jQuery UI, you are in the right place. To discuss development with team members and the community, visit the Developing jQuery UI Forum or in #jquery on irc.freednode.net.
For contributors
If you want to help and provide a patch for a bugfix or new feature, please take a few minutes and look at our Getting Involved guide. In particular check out the Coding standards and Commit Message Style Guide.
In general, fork the project, create a branch for a specific change and send a pull request for that branch. Don't mix unrelated changes. You can use the commit message as the description for the pull request.
For committers
When looking at pull requests, first check for proper commit messages.
Do not merge pull requests directly through GitHub's interface.
Fetch the remote first:
git fetch [their-fork.git] [their-branch]
Then cherry-pick the commit(s):
git cherry-pick [sha-of-commit]
If you need to edit the commit message:
git cherry-pick -e [sha-of-commit]
If you need to edit the changes:
git cherry-pick -n [sha-of-commit]
# make changes
git commit --author="[author-name-and-email]"
If it should go to the stable brach, cherry-pick it to stable:
git checkout 1-8-stable
git cherry-pick -x [sha-of-commit-from-master]
NOTE: Do not cherry-pick into 1-8-stable until you have pushed the commit from master upstream.