You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+17-17Lines changed: 17 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -20,43 +20,43 @@ Every week (unless otherwise noted) the jQuery UI team has a meeting to discuss
20
20
21
21
### Environment: minimum required
22
22
23
-
If you are contributing you will need a fork of jquery (see Getting the source). If you just want the source code you could clone jquery ui directly:
23
+
If you are contributing changes you will need a fork of jquery (see [Getting the source](environment-getting-the-source)). If you just want the source code you could clone jquery ui directly:
24
24
25
25
```bash
26
-
$ git clone git://github.com/jquery/jquery-ui.git
27
-
$ cd jquery-ui
26
+
git clone git://github.com/jquery/jquery-ui.git
27
+
cd jquery-ui
28
28
```
29
29
30
-
The tests can run in any local web server. Ideally you should test your patch in appropriate web browsers and if possible run `grunt` to lint the code and run automated tests (this will happen automatically when you create a pull request). See below for setting up Node.js so that the grunt command works.
30
+
The tests can run in any local web server. Ideally you should test your patch in appropriate web browsers and if possible run `grunt` to lint the code and run automated tests (this will happen automatically when you create a pull request). See the [full setup](environment-recommended-setup) for setting up Node.js so that the grunt command works.
31
31
32
32
### Environment: Getting the source
33
33
34
34
* Create a fork of the jQuery UI repo on GitHub at http://github.com/jquery/jquery-ui. This will create a fork of jquery-ui at your username.
35
35
* You may want to clone jquery-ui under the path to your web server. If so, change to the required directory
To lint the JavaScript, HTML, and CSS, as well as run a smoke test in PhantomJS, run grunt:
92
92
93
93
```bash
94
-
$ grunt
94
+
grunt
95
95
```
96
96
97
97
To run the tests for a specific plugin in your browser, open the appropriate file from the `/tests/unit/` directory, for example: `http://localhost/tests/unit/accordion/accordion.html`. The domain will be dependent on your local server configuration; if there is a port, be sure to include it.
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -21,19 +21,19 @@ In general, fork the project, create a branch for a specific change and send a
21
21
pull request for that branch. Don't mix unrelated changes. You can use the commit
22
22
message as the description for the pull request.
23
23
24
-
For more detailed information, see the [contributing page](CONTRIBUTING.md).
24
+
For more information, see the [contributing page](CONTRIBUTING.md).
25
25
26
26
## Running the Unit Tests
27
27
28
-
Run the unit tests manually with appropriate browsers and any local web server. See our environment setup and information on running tests.
28
+
Run the unit tests manually with appropriate browsers and any local web server. See our [environment setup](CONTRIBUTING.md#environment-minimum-required) and [information on running tests](CONTRIBUTING.md#running-the-tests).
29
29
30
30
You can also run the unit tests inside phantomjs by [setting up your environment](CONTRIBUTING.md#user-content-environment-recommended-setup).
31
31
32
32
## Building jQuery UI
33
33
34
34
jQuery UI uses the [Grunt](http://github.com/gruntjs/grunt) build system.
35
35
36
-
To build jQuery UI, [setup your environment]([setting up your environment](CONTRIBUTING.md#user-content-environment-recommended-setup)) and then run the following commands:
36
+
To build jQuery UI, [setup your environment]([setting up your environment](CONTRIBUTING.md#environment-minimum-required)) and then run the following commands:
0 commit comments