酒店预订平台
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

ISSUE_TEMPLATE.md 1.9 KiB

3 years ago
12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  1. Before posting, please see [guidelines for contributing](https://github.com/silviomoreto/bootstrap-select/blob/master/CONTRIBUTING.md). If you're submitting a bug report, see below.
  2. ## Bug reports
  3. A bug is a _demonstrable problem_ that is caused by the code in the repository.
  4. Good bug reports are extremely helpful - thank you!
  5. Guidelines for bug reports:
  6. 1. **Use the GitHub issue search.** Check if the issue has already been
  7. reported.
  8. 2. **Check if the issue has been fixed.** Try to reproduce it using the
  9. latest `master` or development branch in the repository.
  10. 3. **Provide environment details.** Provide your operating system, browser(s),
  11. jQuery version, Bootstrap version, and bootstrap-select version.
  12. 4. **Create an isolated and reproducible test case.** Create a [reduced test
  13. case](http://css-tricks.com/6263-reduced-test-cases/).
  14. 5. **Include a live example.** Make use of jsFiddle or jsBin to share your
  15. isolated test cases.
  16. A good bug report shouldn't leave others needing to chase you up for more
  17. information. Please try to be as detailed as possible in your report. What is
  18. your environment? What steps will reproduce the issue? What browser(s) and OS
  19. experience the problem? What would you expect to be the outcome? All these
  20. details will help people to fix any potential bugs.
  21. Example:
  22. > Short and descriptive example bug report title
  23. >
  24. > A summary of the issue and the browser/OS environment in which it occurs. If
  25. > suitable, include the steps required to reproduce the bug.
  26. >
  27. > 1. This is the first step
  28. > 2. This is the second step
  29. > 3. Further steps, etc.
  30. >
  31. > `<url>` - a link to the reduced test case
  32. >
  33. > Any other information you want to share that is relevant to the issue being
  34. > reported. This might include the lines of code that you have identified as
  35. > causing the bug, and potential solutions (and your opinions on their
  36. > merits).
  37. ## Erase the above text and being typing. Thanks!