| 提交 | 用户 | 时间 | ||
| 58d006 | 1 | # Contributing |
| A | 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/ . | |
| 13 | * 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! | |
| 14 | ||
| 15 | ## Pull Requests | |
| 16 | ||
| 17 | Patches welcome! | |
| 18 | ||
| 19 | For all cases, you should have your own fork of the repo. | |
| 20 | ||
| 21 | To submit a pull request for a **new feature**: | |
| 22 | ||
| 23 | 1. Run the tests. Every pull request for a new feature should have an accompanying unit test. See the README in the `tests/` directory for details. | |
| 24 | 2. Create a new branch off of the `master` branch for your feature, with a name following the pattern `feature/<description>`, where `<description>` is a short description of the new feature. This is particularly helpful when you want to submit multiple pull requests. | |
| 25 | 3. Add a test (or multiple tests) for your feature. Again, see `tests/README.md`. | |
| 26 | 4. Add your new feature, making the test pass. | |
| 27 | 5. Push to your fork and submit the pull request! | |
| 28 | ||
| 29 | To submit a **bug fix**: | |
| 30 | ||
| 31 | 1. Create a new branch off of the `master` branch, with a name following the pattern `bug/<description>`. | |
| 32 | 2. Add a test that demonstrates the bug. | |
| 33 | 3. Make the test pass. | |
| 34 | 4. Push to your fork and submit the pll request! | |
| 35 | ||
| 36 | To submit a **documentation fix**: | |
| 37 | ||
| 38 | 1. Create a new branch off of the `master` branch, with a name following the pattern `docs/<description>`. | |
| 39 | 2. Add your documentation fixes (no tests required). | |
| 40 | 3. Push to your fork and submit the pull request! | |
