PageRenderTime 157ms CodeModel.GetById 26ms RepoModel.GetById 1ms app.codeStats 0ms

/CONTRIBUTING.md

http://github.com/ajanicij/goduckgo
Markdown | 82 lines | 57 code | 25 blank | 0 comment | 0 complexity | a98850aacc813a776ddb68f6ad7345c3 MD5 | raw file
  1. Contributing to GoDuckGo
  2. ========================
  3. If you love Go and DuckDuckGo, then this is
  4. your place. We're waiting for your Pull Request!
  5. Getting Started
  6. ---------------
  7. Before you can do anything, you first need a [GitHub account](https://github.com/signup/free).
  8. This is required because we use GitHub to handle all incoming *Pull Requests* (code modifications)
  9. and *Issues* (bug reports) which cannot be made without a GitHub account.
  10. Submitting a **Bug** or **Suggestion**
  11. --------------------------------------
  12. - Firstly, please make sure the bug is related to the **GoDuckGo** package. If this bug
  13. is about the DuckDuckGo API, or the relevancy of the search results, please visit DuckDuckGo's
  14. feedback page at <https://duckduckgo.com/feedback>.
  15. - Check the **GoDuckGo** [issues](https://github.com/ajanicij/goduckgo/issues) to see if
  16. an issue already exists for the given bug or suggestion:
  17. - If one doesn't exist, create a GitHub issue in the **GoDuckGo** repository:
  18. - Clearly describe the bug/improvement, including steps to reproduce when it is a bug.
  19. - If one already exists, please add any additional comments you have regarding the matter.
  20. If you're submitting a **pull request** (bugfix/addition):
  21. - Fork the **GoDuckGo** repository on GitHub.
  22. Making Changes
  23. --------------
  24. - Before making any changes, make sure your [Go environment](http://golang.org/doc/install) is setup.
  25. - Run `gofmt` and `go vet` commands to clean up your code.
  26. - Make sure your commits are of a reasonable size. They shouldn't be too big.
  27. - Make sure your commit messages effectively explain what changes have been made.
  28. ```shell
  29. main.go: Handle error when Icon is empty
  30. ```
  31. is much better than:
  32. ```shell
  33. annoying error for empty icon is fixed now
  34. ```
  35. - Make sure you have added the necessary tests for your changes.
  36. - Make sure your change doesn't affect backwards compatibility.
  37. Submitting Changes
  38. ------------------
  39. 1. Commit your changes.
  40. ```shell
  41. git commit -am "My first commit!"
  42. ```
  43. 2. Get your commit history [how you like it](http://book.git-scm.com/4_interactive_rebasing.html).
  44. ```shell
  45. git rebase -i origin/master
  46. ```
  47. or
  48. ```shell
  49. git pull --rebase origin/master
  50. ```
  51. 3. Push your forked repository back to GitHub.
  52. ```shell
  53. git push
  54. ```
  55. 4. Add your info to the [AUTHORS.md page](https://github.com/ajanicij/goduckgo/blob/master/AUTHORS.md).
  56. 5. Go into GitHub and submit a [pull request!](http://help.github.com/send-pull-requests/) to the
  57. **GoDuckGo** repository.