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
Help us make UI-Router better! If you think you might have found a bug, or some other weirdness, start by making sure
5
+
it hasn't already been reported. You can [search through existing issues](https://github.com/angular-ui/ui-router/search?q=wat%3F&type=Issues)
6
+
to see if someone's reported one similar to yours.
7
+
8
+
If not, then [create a plunkr](http://bit.ly/UIR-Plunk) that demonstrates the problem (try to use as little code
9
+
as possible: the more minimalist, the faster we can debug it).
10
+
11
+
Next, [create a new issue](https://github.com/angular-ui/ui-router/issues/new) that briefly explains the problem,
12
+
and provides a bit of background as to the circumstances that triggered it. Don't forget to include the link to
13
+
that plunkr you created!
14
+
15
+
**Note**: If you're unsure how a feature is used, or are encountering some unexpected behavior that you aren't sure
16
+
is a bug, it's best to talk it out on
17
+
[StackOverflow](http://stackoverflow.com/questions/ask?tags=angularjs,angular-ui-router) before reporting it. This
18
+
keeps development streamlined, and helps us focus on building great software.
19
+
20
+
21
+
Issues only! |
22
+
-------------|
23
+
Please keep in mind that the issue tracker is for *issues*. Please do *not* post an issue if you need help or support. Instead, see one of the above-mentioned forums or [IRC](irc://irc.freenode.net/#angularjs). |
24
+
25
+
####Purple Labels
26
+
A purple label means that **you** need to take some further action.
27
+
-: Your issue is not specific enough, or there is no clear action that we can take. Please clarify and refine your issue.
28
+
-: Please [create a plunkr](http://bit.ly/UIR-Plunk)
29
+
-: We suspect your issue is really a help request, or could be answered by the community. Please ask your question on [StackOverflow](http://stackoverflow.com/questions/ask?tags=angularjs,angular-ui-router). If you determine that is an actual issue, please explain why.
30
+
31
+
If your issue gets labeled with purple label, no further action will be taken until you respond to the label appropriately.
32
+
33
+
# Contribute
34
+
35
+
**(1)** See the **[Developing](#developing)** section below, to get the development version of UI-Router up and running on your local machine.
36
+
37
+
**(2)** Check out the [roadmap](https://github.com/angular-ui/ui-router/milestones) to see where the project is headed, and if your feature idea fits with where we're headed.
38
+
39
+
**(3)** If you're not sure, [open an RFC](https://github.com/angular-ui/ui-router/issues/new?title=RFC:%20My%20idea) to get some feedback on your idea.
40
+
41
+
**(4)** Finally, commit some code and open a pull request. Code & commits should abide by the following rules:
42
+
43
+
-*Always* have test coverage for new features (or regression tests for bug fixes), and *never* break existing tests
44
+
- Commits should represent one logical change each; if a feature goes through multiple iterations, squash your commits down to one
45
+
- Make sure to follow the [Angular commit message format](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format) so your change will appear in the changelog of the next release.
46
+
- Changes should always respect the coding style of the project
47
+
48
+
49
+
50
+
# Developing
51
+
52
+
UI-Router uses <code>grunt >= 0.4.x</code>. Make sure to upgrade your environment and read the
@@ -31,8 +31,8 @@ Check out the sample app: http://angular-ui.github.io/ui-router/sample/
31
31
32
32
## Get Started
33
33
34
-
**(1)** Get UI-Router in one of 4 ways:
35
-
- clone & [build](#developing) this repository
34
+
**(1)** Get UI-Router in one of the following ways:
35
+
- clone & [build](CONTRIBUTING.md#developing) this repository
36
36
-[download the release](http://angular-ui.github.io/ui-router/release/angular-ui-router.js) (or [minified](http://angular-ui.github.io/ui-router/release/angular-ui-router.min.js))
37
37
- via **[Bower](http://bower.io/)**: by running `$ bower install angular-ui-router` from your console
38
38
- or via **[npm](https://www.npmjs.org/)**: by running `$ npm install angular-ui-router` from your console
*[Learn Angular.js using UI-Router](http://youtu.be/QETUuZ27N0w) (LearnCode.academy)
237
238
238
-
## Report an Issue
239
-
240
-
Help us make UI-Router better! If you think you might have found a bug, or some other weirdness, start by making sure
241
-
it hasn't already been reported. You can [search through existing issues](https://github.com/angular-ui/ui-router/search?q=wat%3F&type=Issues)
242
-
to see if someone's reported one similar to yours.
243
-
244
-
If not, then [create a plunkr](http://plnkr.co/edit/u18KQc?p=preview) that demonstrates the problem (try to use as little code
245
-
as possible: the more minimalist, the faster we can debug it).
246
-
247
-
Next, [create a new issue](https://github.com/angular-ui/ui-router/issues/new) that briefly explains the problem,
248
-
and provides a bit of background as to the circumstances that triggered it. Don't forget to include the link to
249
-
that plunkr you created!
250
-
251
-
**Note**: If you're unsure how a feature is used, or are encountering some unexpected behavior that you aren't sure
252
-
is a bug, it's best to talk it out in the
253
-
[Google Group](https://groups.google.com/forum/#!categories/angular-ui/router) or on
254
-
[StackOverflow](http://stackoverflow.com/questions/ask?tags=angularjs,angular-ui-router) before reporting it. This
255
-
keeps development streamlined, and helps us focus on building great software.
256
-
257
-
Please keep in mind that the issue tracker is for *issues*. Please do *not* post an issue if you need help or support. Instead, see one of the above-mentioned forums or [IRC](irc://irc.freenode.net/#angularjs).
258
-
259
-
260
-
## Contribute
261
-
262
-
**(1)** See the **[Developing](#developing)** section below, to get the development version of UI-Router up and running on your local machine.
263
-
264
-
**(2)** Check out the [roadmap](https://github.com/angular-ui/ui-router/issues/milestones) to see where the project is headed, and if your feature idea fits with where we're headed.
265
-
266
-
**(3)** If you're not sure, [open an RFC](https://github.com/angular-ui/ui-router/issues/new?title=RFC:%20My%20idea) to get some feedback on your idea.
267
-
268
-
**(4)** Finally, commit some code and open a pull request. Code & commits should abide by the following rules:
269
-
270
-
-*Always* have test coverage for new features (or regression tests for bug fixes), and *never* break existing tests
271
-
- Commits should represent one logical change each; if a feature goes through multiple iterations, squash your commits down to one
272
-
- Make sure to follow the [Angular commit message format](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format) so your change will appear in the changelog of the next release.
273
-
- Changes should always respect the coding style of the project
274
-
275
-
276
-
277
-
## Developing
278
-
279
-
UI-Router uses <code>grunt >= 0.4.x</code>. Make sure to upgrade your environment and read the
0 commit comments