Repository files navigation

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 tojqueryui.com to get started. Or visit theUsing 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 theDeveloping jQuery UI Forum or in #jquery on irc.freednode.net.

If you want to help and provide a patch for a bugfix or new feature, please takea few minutes and look atour Getting Involved guide.In particular check out theCoding standardsandCommit Message Style Guide.

In general, fork the project, create a branch for a specific change and send apull request for that branch. Don't mix unrelated changes. You can use the commitmessage as the description for the pull request.

Run the unit tests with a local server that supports PHP. No database is required. Pre-configured php local servers are available for Windows and Mac. Here are some options:

• Windows:WAMP download
• Mac:MAMP download
• Linux:Setting up LAMP
• Mongoose (most platforms)

jQuery UI uses thegrunt build system. Building jQuery UI requires node.js and a command line zip program.

Install grunt.

npm install grunt -g

Clone the jQuery UI git repo.

git clone git://github.com/jquery/jquery-ui.git

cd jquery-ui

Install node modules.

npm install

Run grunt.

grunt build

There are many other tasks that can be run through grunt. For a list of all tasks:

grunt --help

When looking at pull requests, first check forproper commit messages.

Do not merge pull requests directly through GitHub's interface.Most pull requests are a single commit; cherry-picking will avoid creating a merge commit.It's also common for contributors to make minor fixes in an additional one or two commits.These should be squashed before landing in master.

Make sure the author has a valid name and email address associated with the commit.

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 changesgit commit --author="[author-name-and-email]"

If it should go to the stable brach, cherry-pick it to stable:

git checkout 1-8-stablegit 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.