diff options
author | Scott González <scott.gonzalez@gmail.com> | 2014-05-20 16:25:26 -0400 |
---|---|---|
committer | Scott González <scott.gonzalez@gmail.com> | 2014-05-20 16:25:26 -0400 |
commit | bb4f5f9c1e28407e53b286351eea823352fcefce (patch) | |
tree | 0ba1dd91e178699a358d0c657a26809a6eb2cb33 /README.md | |
parent | f5e8041ebf1e0b36d67d1716a0cfec44692fabb8 (diff) | |
download | jquery-ui-bb4f5f9c1e28407e53b286351eea823352fcefce.tar.gz jquery-ui-bb4f5f9c1e28407e53b286351eea823352fcefce.zip |
README: Remove content that exists on the contribute site
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 39 |
1 files changed, 1 insertions, 38 deletions
@@ -15,7 +15,7 @@ To discuss development with team members and the community, visit the [Developin 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](http://wiki.jqueryui.com/w/page/35263114/Getting-Involved). In particular check out the [Coding standards](http://wiki.jqueryui.com/w/page/12137737/Coding-standards) -and [Commit Message Style Guide](http://wiki.jqueryui.com/w/page/25941597/Commit-Message-Style-Guide). +and [Commit Message Style Guide](http://contribute.jquery.org/commits-and-pull-requests/#commit-guidelines). 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 @@ -57,40 +57,3 @@ grunt concat # For a list of all tasks: grunt --help ``` - - -## For committers - -When looking at pull requests, first check for [proper commit messages](http://wiki.jqueryui.com/w/page/12137724/Bug-Fixing-Guide). - -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 changes - git commit --author="[author-name-and-email]" - -If it should go to the stable branch, cherry-pick it to stable: - - git checkout 1-10-stable - git cherry-pick -x [sha-of-commit-from-master] - -*NOTE: Do not cherry-pick into 1-10-stable until you have pushed the commit from master upstream.* |