If you love Go and DuckDuckGo, then this is your place. We're waiting for your Pull Request!
Before you can do anything, you first need a GitHub account. This is required because we use GitHub to handle all incoming Pull Requests (code modifications) and Issues (bug reports) which cannot be made without a GitHub account.
-
Firstly, please make sure the bug is related to the GoDuckGo package. If this bug is about the DuckDuckGo API, or the relevancy of the search results, please visit DuckDuckGo's feedback page at https://duckduckgo.com/feedback.
-
Check the GoDuckGo issues to see if an issue already exists for the given bug or suggestion:
- If one doesn't exist, create a GitHub issue in the GoDuckGo repository:
- Clearly describe the bug/improvement, including steps to reproduce when it is a bug.
- If one already exists, please add any additional comments you have regarding the matter.
- If one doesn't exist, create a GitHub issue in the GoDuckGo repository:
If you're submitting a pull request (bugfix/addition):
- Fork the GoDuckGo repository on GitHub.
-
Before making any changes, make sure your Go environment is setup.
-
Run
gofmt
andgo vet
commands to clean up your code. -
Make sure your commits are of a reasonable size. They shouldn't be too big.
-
Make sure your commit messages effectively explain what changes have been made.
main.go: Handle error when Icon is empty
is much better than:
annoying error for empty icon is fixed now
-
Make sure you have added the necessary tests for your changes.
-
Make sure your change doesn't affect backwards compatibility.
- Commit your changes.
git commit -am "My first commit!"
- Get your commit history how you like it.
git rebase -i origin/master
or
git pull --rebase origin/master
- Push your forked repository back to GitHub.
git push
-
Add your info to the AUTHORS.md page.
-
Go into GitHub and submit a pull request! to the GoDuckGo repository.