| Server IP : 74.208.127.88 / Your IP : 3.135.211.95 Web Server : Apache/2.4.41 (Ubuntu) System : Linux ubuntu 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 User : www-data ( 33) PHP Version : 7.4.3-4ubuntu2.29 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /var/www/html/admin/assets/plugins/bootstrap-datepicker/ |
Upload File : |
# Contributing ## Support requests 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). ## Issues If you've found a bug in bootstrap-datepicker, we want to know about it! However, please keep the following in mind: * 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/ . * 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/ . * 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! ## Pull Requests Patches welcome! For all cases, you should have your own fork of the repo. To submit a pull request for a **new feature**: 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. 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. 3. Add a test (or multiple tests) for your feature. Again, see `tests/README.md`. 4. Add your new feature, making the test pass. 5. Push to your fork and submit the pull request! To submit a **bug fix**: 1. Create a new branch off of the `master` branch, with a name following the pattern `bug/<description>`. 2. Add a test that demonstrates the bug. 3. Make the test pass. 4. Push to your fork and submit the pll request! To submit a **documentation fix**: 1. Create a new branch off of the `master` branch, with a name following the pattern `docs/<description>`. 2. Add your documentation fixes (no tests required). 3. Push to your fork and submit the pull request!