Skip to content

Commit f6c89e9

Browse files
authored
Merge pull request #30 from paceaux/develop
merge contribution guidelines to master
2 parents 8163fae + c342e01 commit f6c89e9

File tree

1 file changed

+44
-0
lines changed

1 file changed

+44
-0
lines changed

CONTRIBUTING.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# How to Contribute to SelectorHound
2+
3+
## Did you find a bug?
4+
5+
1. Check and see if it's already been reported under [issues](https://github.com/paceaux/selector-finder/issues).
6+
* Add your own comments to the issue if you have more information to add
7+
* Exact parameters you passed in
8+
* Relevant excerpts from your log.txt file
9+
10+
2. If it hasn't been reported, [open a new issue](https://github.com/paceaux/selector-finder/issues/new)
11+
* Include a title and clear description
12+
* Include the exact parameters you passed in
13+
* include a sample of the output from your log.txt file
14+
* Include your version of node and npm
15+
16+
## Would you like a new feature?
17+
18+
1. Check [our enhancements](https://github.com/paceaux/selector-finder/labels/enhancement).
19+
2. If yours isn't there, open a new issue and set the label as "enhancement";
20+
* Use the title to explain in 1 sentence what you're looking for
21+
* In the description, explain in a few bullet points:
22+
* How a developer would know the feature has been delivered
23+
* What the motivation is for this feature?
24+
25+
## Would you like to contribute to this?
26+
27+
0. Find an issue that you'd like to work on
28+
1. Clone this repository
29+
2. Make a branch off of `develop` labeled `[issue number]-[short description]`
30+
3. Do your work
31+
4. JSDoc your code
32+
5. Write unit tests
33+
6. Run the linter
34+
7. Submit a PR to `develop`
35+
8. Include how you tested the CLI
36+
9. Indicate whether this is a patch, minor, or major change
37+
38+
### What happens after your PR is approved?
39+
40+
1. It will be merged into `develop`
41+
2. The maintainers will run tests and test the CLI with more examples
42+
3. They may or may not include additional issues in the merge to develop
43+
4. When develop is ready for a release, a maintainer will increment the package version and merge it into `master`
44+
5. The maintainer will tag the release in `master` and push it to npm

0 commit comments

Comments
 (0)