Skip to content

Latest commit

 

History

History
48 lines (23 loc) · 1.66 KB

CONTRIBUTING.md

File metadata and controls

48 lines (23 loc) · 1.66 KB

Contributing to dw project

Option1. Search your symptom or new feature in existing issues

Before submitting a new issue, you may find your symptom in past discussions in Issues.

Option2. Submit a new issue

If you cannot find your symptom or , then please share the problem with us by submitting a new issue.

Option3. Fork/Branch the repository, commit your code with signoff, and send pull request

Developer Certificate of Origin (DCO)

dw have tried to make it as easy as possible to make contributions. This applies to how we handle the legal aspects of contribution. We use the same approach - the DCO1.1.txt that the Linux® Kernel community uses to manage code contributions. We simply ask that when submitting a patch for review, the developer must include a sign-off statement in the commit message. Here is an example Signed-off-by line, which indicates that the submitter accepts the DCO:

Signed-off-by: John Doe <john.doe@example.com>

You can include this automatically when you commit a change to your local git repository using the following command:

git commit -s

Example of contribution steps

  1. Push fork button.
  2. Clone your forked repo (git clone git@github.com:YOURNAME/dw.git)
  3. Add your changes (git add MODIFIED_FILES)
  4. Commit your changes (git commit -s -m 'Add some feature')
  5. Push to the branch (git push origin main)
  6. In Pull requests tab, push New pull request button.
  7. Push Create pull request button.