From c15abe6c718bf71b6f93b0afe1907fee810ff197 Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Thu, 28 Dec 2017 11:29:55 +0100 Subject: [PATCH 1/2] Create ISSUE_TEMPLATE.md --- ISSUE_TEMPLATE.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 ISSUE_TEMPLATE.md diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md new file mode 100644 index 000000000..24a44c03c --- /dev/null +++ b/ISSUE_TEMPLATE.md @@ -0,0 +1,5 @@ +### Expected behavior + +### Actual behavior + +### Steps to reprodcue From d3200d5be3a85ed8604303ea3de9c2d4f544d67f Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Thu, 28 Dec 2017 11:37:24 +0100 Subject: [PATCH 2/2] Create CONTRIBUTING.md --- CONTRIBUTING.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 000000000..78e6ac5e4 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,18 @@ +# How to contribute +Thanks for taking your time to read this. We're thrilled you're reading this because we the help from the community to keep improving this project. + +## Testing +We have a handful of Cucumber features, but most of our testbed consists of RSpec examples. Please write RSpec examples for new code you create. + +## Submitting changes +Please send a [GitHub Pull Request](https://github.com/Hacker0x01/react-datepicker/pull/new/master) with a clear list of what you've done (read more about [pull requests](http://help.github.com/pull-requests/)). When you send a pull request, we will love you forever if you include a test to cover your changed. We can always use more test coverage. +Always write a clear log message for your commits. One-line messages are fine for small changes, but bigger changes should look like this: + $ git commit -m "A summary of the commit + > + > A paragraph describing what changed and its impact." + +## Coding conventions +Start reading our code, and you'll get the hang of it. We optimize for readability: + * We use prettier for code styling. Don't worry about tabs vs spaces, or how to indent your code. + * We use ESlint for all other coding standards. We try to be consistent and helpful. + * This is open source software. Consider the people who will read your code, and make it look nice for them. It's sort of like driving a car: Perhaps you love doing donuts when you're alone, but with passengers, the goal is to make the ride as smooth as possible.