4 Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
6 ## PRs and Code contributions
9 * Follow the [JavaScript Standard Style](http://standardjs.com/) and `npm run lint`.
10 * If you fix a bug, add a test.
14 Use the `master` branch for bug fixes or minor work that is intended for the
15 current release stream.
17 Use the correspondingly named branch, e.g. `5.0`, for anything intended for
18 a future release of Express.
20 ## Steps for contributing
22 1. [Create an issue](https://github.com/expressjs/express/issues/new) for the
23 bug you want to fix or the feature that you want to add.
24 2. Create your own [fork](https://github.com/expressjs/express) on github, then
26 3. Write your code in your local copy. It's good practice to create a branch for
27 each new issue you work on, although not compulsory.
28 4. To run the test suite, first install the dependencies by running `npm install`,
30 5. Ensure your code is linted by running `npm run lint` -- fix any issue you
32 6. If the tests pass, you can commit your changes to your fork and then create
33 a pull request from there. Make sure to reference your issue from the pull
34 request comments by including the issue number e.g. `#123`.
36 ## Issues which are questions
38 We will typically close any vague issues or questions that are specific to some
39 app you are writing. Please double check the docs and other references before
40 being trigger happy with posting a question issue.
42 Things that will help get your question issue looked at:
44 * Full and runnable JS code.
45 * Clear description of the problem or unexpected behavior.
46 * Clear description of the expected result.
47 * Steps you have taken to debug it yourself.
49 If you post a question and do not outline the above items or make it easy for
50 us to understand and reproduce your issue, it will be closed.