# This ensures that you're running the most recent Sizzle and QUnit # I like to run "make clean" before any bug fixing sessions # up to date as jQuery receives new commits # Get in the habit of pulling in the "upstream" master to stay $ git remote add upstream git:///jquery/jquery.git
# Add the jQuery master as a remote, I label mine "upstream" $ git clone Change directory to the newly created dir jquery/ # Change directory to your web root directory, whatever that might be: # Create a fork of the jQuery repo on github at # Specifically you'll probably end up doing something like this: # code and follow the build instructions on your system:
# If you do not have NodeJS installed please download the # If you do not have git installed, check these out: # Remy Sharp has a created a useful node based web server for use wherever node.js is available: # set up with some form of "localhost" http server and that it's running. # There are some assumptions made here, one being that you're Jquery-patching-tips.sh # Tips for jQuery Bug Patching If bug fixing is not your thing, don’t worry, all of these tips apply to new features and enhancements as well! This guide was originally published on the jQuery Blog.
If you’ve ever been interested in contributing to jQuery, but simply had no idea how to get started, I’ve created the following jQuery Bug Fixing Guide to walk through the steps of fixing bugs and contributing your fixes to the jQuery core. It’s preserved in its entirety for historic record only. This article describes processes and policies that are no longer in use.