Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 42 lines (27 sloc) 2.556 kB
bbd6d4a @eternicode Add CONTRIBUTING.md file
authored
1 # Contributing
2
3 ## Support requests
4
5 The issue tracker is not the place for support requests. If you get stuck with bootstrap-datepicker, it's very likely that the fine folks at [StackOverflow](http://stackoverflow.com/) will be able to help you; simply describe the problem you're having and provide them a link to the repo (so they know what code you're using). Another option is to post to the [bootstrap-datepicker google group](https://groups.google.com/group/bootstrap-datepicker).
6
7 ## Issues
8
9 If you've found a bug in bootstrap-datepicker, we want to know about it! However, please keep the following in mind:
10
11 * This is not the bootstrap-datepicker from [eyecon.ro](http://www.eyecon.ro/bootstrap-datepicker/). Stefan provided the initial code for bootstrap-datepicker, but this repo is divergent from his codebase. Please make sure you're using either the latest tagged version or the latest master from https://github.com/eternicode/bootstrap-datepicker/ .
12 * A working example of the bug you've found is *much* easier to work with than a description alone. If possible, please provide a link to a demonstration of the bug, perhaps using http://jsfiddle.net/ .
1f556f2 @eternicode Add contributing note about CDN assets for testing
authored
13 * CDN-backed assets can be found at http://bsdp-assets.blackcherry.us/ . These should be used *only* for building test cases, as they may be removed or changed at any time.
bbd6d4a @eternicode Add CONTRIBUTING.md file
authored
14 * Finally, it's possible someone else has already reported the same bug you have. Please search the issue tracker for similar issues before posting your own. Thanks!
15
16 ## Pull Requests
17
18 Patches welcome!
19
20 For all cases, you should have your own fork of the repo.
21
22 To submit a pull request for a **new feature**:
23
8f88888 @eternicode Update various READMEs
authored
24 1. Run the tests. Every pull request for a new feature should have an accompanying unit test and docs changes. See the README in the `tests/` and `docs/` directories for details.
25 2. Create a new branch off of the `master` branch for your feature. This is particularly helpful when you want to submit multiple pull requests.
bbd6d4a @eternicode Add CONTRIBUTING.md file
authored
26 3. Add a test (or multiple tests) for your feature. Again, see `tests/README.md`.
27 4. Add your new feature, making the test pass.
28 5. Push to your fork and submit the pull request!
29
30 To submit a **bug fix**:
31
8f88888 @eternicode Update various READMEs
authored
32 1. Create a new branch off of the `master` branch.
bbd6d4a @eternicode Add CONTRIBUTING.md file
authored
33 2. Add a test that demonstrates the bug.
34 3. Make the test pass.
8f88888 @eternicode Update various READMEs
authored
35 4. Push to your fork and submit the pull request!
bbd6d4a @eternicode Add CONTRIBUTING.md file
authored
36
37 To submit a **documentation fix**:
38
8f88888 @eternicode Update various READMEs
authored
39 1. Create a new branch off of the `master` branch.
bbd6d4a @eternicode Add CONTRIBUTING.md file
authored
40 2. Add your documentation fixes (no tests required).
41 3. Push to your fork and submit the pull request!
Something went wrong with that request. Please try again.