-
Notifications
You must be signed in to change notification settings - Fork 203
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update and rename contributing.md to CONTRIBUTING.md
- Loading branch information
1 parent
79cfda4
commit 418a366
Showing
2 changed files
with
38 additions
and
10 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,38 @@ | ||
Contributing to Store | ||
======================= | ||
|
||
The New York Times team welcomes contributions of all kinds, from simple bug reports through documentation, test cases, | ||
bugfixes, and features. | ||
|
||
DOs and DON'Ts | ||
-------------- | ||
|
||
* DO follow our coding style (as described below) | ||
* DO give priority to the current style of the project or file you're changing even if it diverges from the general guidelines. | ||
* DO include tests when adding new features. When fixing bugs, start with adding a test that highlights how the current behavior is broken. | ||
* DO keep the discussions focused. When a new or related topic comes up it's often better to create new issue than to side track the discussion. | ||
* DO run all Gradle verification tasks (`./gradlew check`) before submitting a pull request | ||
|
||
* DO NOT send PRs for style changes. | ||
* DON'T surprise us with big pull requests. Instead, file an issue and start a discussion so we can agree on a direction before you invest a large amount of time. | ||
* DON'T commit code that you didn't write. If you find code that you think is a good fit, file an issue and start a discussion before proceeding. | ||
* DON'T submit PRs that alter licensing related files or headers. If you believe there's a problem with them, file an issue and we'll be happy to discuss it. | ||
|
||
|
||
Coding Style | ||
------------ | ||
|
||
The coding style employed here is fairly conventional Java - indentations are four spaces, class | ||
names are PascalCased, identifiers and methods are camelCased. | ||
|
||
Workflow | ||
-------- | ||
|
||
We love Github issues! Before working on any new features, please open an issue so that we can agree on the | ||
direction, and hopefully avoid investing a lot of time on a feature that might need reworking. | ||
|
||
Small pull requests for things like typos, bugfixes, etc are always welcome. | ||
|
||
Please note that we will not accept pull requests for style changes. | ||
|
||
|
This file was deleted.
Oops, something went wrong.