1 | # Contributing to parallel-webpack
|
2 |
|
3 | Thank you for contributing to `parallel-webpack`!
|
4 |
|
5 | This project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md) By participating you agree to comply with its terms.
|
6 |
|
7 | #### Table Of Contents
|
8 |
|
9 | [How Can I Contribute?](#how-can-i-contribute)
|
10 | * [Improve Documentation](#improve-documentation)
|
11 | * [Reporting Bugs](#reporting-bugs)
|
12 | * [Writing Code](#writing-code)
|
13 | * [Pull Requests](#pull-requests)
|
14 |
|
15 |
|
16 | ## How can I contribute?
|
17 |
|
18 | ### Improve documentation
|
19 | Most simple way to contribute is improving our documentation. Fixing typo's, fixing errors, explaining something better,
|
20 | more examples etc. If your work would be a big change, open an issue first. For smaller changes feel free to open a PR
|
21 | directly.
|
22 |
|
23 | Use common sense to decide if you need an issue or not. Generally if you change more than a few paragraphs, multiple
|
24 | files etc, it is better to open an issue and explain your change.
|
25 |
|
26 | ### Reporting Bugs
|
27 |
|
28 | If you encounter any issues with `parallel-webpack` don't hesitate to report it. While reporting your bug make sure you
|
29 | follow the guidelines below. It helps maintainers to understand and reproduce the problem.
|
30 |
|
31 | * **Use a clear and descriptive title** for the issue to identify the problem.
|
32 | * **Provide configuration you used** which is critical for reproducing problem in most cases.
|
33 | * **Provide system details you used** to identify if the problem is system specific. I.e: operating system, node version, webpack version you used etc.
|
34 | * **Describe the exact steps which reproduce the problem** in as many details as possible.
|
35 | * **Describe the behavior you observed after following the steps** and point out what exactly is the problem with that behavior.
|
36 | * **Explain which behavior you expected to see instead and why.**
|
37 |
|
38 | > **Note:** If you find a **Closed** issue that seems like it is the same thing that you're experiencing, open a new issue and include a link to the original issue in the body of your new one.
|
39 |
|
40 |
|
41 | ### Writing code
|
42 |
|
43 | Find an issue you want to work on, or if you have your own idea create an issue. You might find an issue assigned. Double-check
|
44 | if somebody else is working on the same issue.
|
45 |
|
46 | #### Local development
|
47 |
|
48 | It usually is a good idea to create a dummy repository to run your changes.
|
49 |
|
50 | While writing code make sure you follow this guidelines:
|
51 | * Use 4 space indentation.
|
52 | * Always use strict equality checks `===` instead of `==`.
|
53 | * Make sure your code runs on node 6.
|
54 | * Write tests and run them. Check coverage before submitting.
|
55 | * Write documentation for your code.
|
56 |
|
57 | ### Pull Requests
|
58 |
|
59 | * Non-trivial changes are often best discussed in an issue first, to prevent you from doing unnecessary work.
|
60 | * For ambitious tasks, you should try to get your work in front of the community for feedback as soon as possible. Open a pull request as soon as you have done the minimum needed to demonstrate your idea. At this early stage, don't worry about making things perfect, or 100% complete. Add a [WIP] prefix to the title, and describe what you still need to do. This lets reviewers know not to nit-pick small details or point out improvements you already know you need to make.
|
61 | * New features should be accompanied with tests and documentation.
|
62 | * Don't include unrelated changes.
|
63 | * Make the pull request from a [topic branch](https://github.com/dchelimsky/rspec/wiki/Topic-Branches), not master.
|
64 | * Use a clear and descriptive title for the pull request and commits.
|
65 | * Write a convincing description of why we should land your pull request. It's your job to convince us. Answer "why" it's needed and provide use-cases.
|
66 | * You might be asked to do changes to your pull request. There's never a need to open another pull request. [Just update the existing one.](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md)
|
67 | * Be patient, we might not find time to check on your pull requests immediately. It will be checked eventually.
|