PageRenderTime 62ms CodeModel.GetById 48ms app.highlight 10ms RepoModel.GetById 2ms app.codeStats 0ms

Markdown | 70 lines | 46 code | 24 blank | 0 comment | 0 complexity | 4f1ecdb68b8e8963d833862bd10f175a MD5 | raw file
 1# Contributing to the **DuckDuckGo** repository
 3At DuckDuckGo, we truly appreciate our community members taking the time to contribute to our open-source repositories. In an effort to ensure contributions are easy for you to make and for us to manage, we have written some guidelines that we ask our contributors to follow so that we can handle pull requests in a timely manner with as little friction as possible.
 5## Getting Started
 7Before 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.
 9## Submitting a **Bug** or **Suggestion**
11- Firstly, please make sure the bug is related to the **DuckDuckGo** repository. If this bug is about the DuckDuckGo API, or the relevancy of our search results, please visit our feedback page at <>. If you're unsure, its best to use the feedback page (your message will be passed along to the correct people).
13- Check the **DuckDuckGo** [issues](#link-to-issues) to see if an issue already exists for the given bug or suggestion
14  - If one doesn't exist, create a GitHub issue in the **DuckDuckGo** repository
15    - Clearly describe the bug/improvemnt, including steps to reproduce when it is a bug
16  - If one already exists, please add any additional comments you have regarding the matter
18If you're submitting a **pull request** (bugfix/addition):
19- Fork the **DuckDuckGo** repository on GitHub
21## Making Changes
23- Before making any changes, refer to the [DuckDuckHack Styleguide]( to ensure your changes are made in the correct fashion
24- Make sure your commits are of a reasonable size. They shouldn't be too big (or too small)
25- Make sure your commit messages effectively explain what changes have been made, and please identify which instant answer or file has been modified:
27  ```shell
28 - Added the example commit message because it was missing
29  ```
31  is much better than:
33  ```shell
34  <bad_commit_example>
35  ```
37- Make sure you have added the necessary tests for your changes
38- Run `dzil test` (executes all tests in t/) to ensure nothing else was accidentally broken
39- If your change affects an instant answer, remember to add yourself to the Metadata attribution list in the appropriate `.pm` file
41## Submitting Changes
431. Commit your changes.
45  ```shell
46  git commit -a -m "My first instant answer that does X is ready to go!"
47  ```
492. Get your commit history [how you like it](
51  ```shell
52  git rebase -i origin/master
53  ```
55  or
57  ```shell
58  git pull --rebase origin/master
59  ```
613. Push your forked repository back to GitHub.
63  ```shell
64  git push
65  ```
674. Add your info to the instant answer so we can give you credit for it on the [Goodies page]( You'll see your name or handle on the live site!
68Check out the [Metadata README]( for detailed instructions on how to include your name and links.
705. Go into GitHub and submit a [pull request!]( to the **DuckDuckGo** repository, making sure to use the **DuckDuckGo** repository's **[Pull Request Template](**. This will let us know about your changes and start the conversation about integrating it into the live code.