This repository has been archived by the owner on Nov 9, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 66
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated documentation and added contributing guide
- Loading branch information
1 parent
61de236
commit ef5c833
Showing
2 changed files
with
62 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
# Contributing | ||
|
||
First off, thank you for considering contributing to USB Canary. | ||
|
||
### 1. Where do I go from here? | ||
|
||
If you've noticed a bug or have a question [search the issue tracker](https://github.com/probablynotablog/usb-canary/issues?q=something) | ||
to see if someone else in the community has already created a ticket. If not, go ahead and [make one](https://github.com/probablynotablog/usb-canary/issues/new)! | ||
|
||
### 2. Fork & create a branch | ||
|
||
If this is something you think you can fix, then [fork USB Canary](https://help.github.com/articles/fork-a-repo) | ||
and create a branch with a descriptive name. | ||
|
||
A good branch name would be (where issue #325 is the ticket you're working on): | ||
|
||
```sh | ||
git checkout -b 325-add-windows-support | ||
``` | ||
|
||
#### 3. Did you find a bug? | ||
|
||
* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/probablynotablog/usb-canary/issues). | ||
|
||
* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/probablynotablog/usb-canary/issues/new). | ||
Be sure to include a **title and clear description**, as much relevant information as possible - use the relevant bug report templates to create the issue. | ||
|
||
### 5. Implement your fix or feature | ||
|
||
At this point, you're ready to make your changes! Feel free to ask for help; everyone is a beginner at first. | ||
|
||
### 6. Test your changes | ||
|
||
We don't currently have an automated test suite, so it's up to you to test your bug fix or feature to ensure it does not impact exsisting features, unless that feature was really a bug and you're fixing it. If you're unable to test your new feature, reach out to one of the maintainers who will be happy to help. (It may take longer to be accepted) | ||
|
||
### 7. Make a Pull Request | ||
|
||
At this point, you should switch back to your master branch and make sure it's | ||
up to date with USB Canary's master branch. | ||
|
||
Push it! | ||
|
||
Finally, go to GitHub and [make a Pull Request](https://help.github.com/articles/creating-a-pull-request). | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters