You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+17-11
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,22 @@
1
1
# Contributing
2
2
3
-
Thanks for your interest in contributing to `react-tailwindcss-datepicker`! Please take a moment to review this document **before submitting a pull request**.
3
+
Thanks for your interest in contributing to `react-tailwindcss-datepicker`! Please take a moment to
4
+
review this document **before submitting a pull request**.
4
5
5
-
-[Pull requests](#pull-requests)
6
-
-[Installation](#installation)
7
-
-[Coding standards](#coding-standards)
8
-
-[Running playground](#running-playgrounds)
9
-
-[Before you make a Pull Request](#before-you-make-a-pull-request)
6
+
-[Pull requests](#pull-requests)
7
+
-[Installation](#installation)
8
+
-[Coding standards](#coding-standards)
9
+
-[Running playground](#running-playgrounds)
10
+
-[Before you make a Pull Request](#before-you-make-a-pull-request)
10
11
11
12
## Pull requests
12
13
13
14
**Please ask first before starting work on any significant new features.**
14
15
15
-
It's never a fun experience to have your pull request declined after investing a lot of time and effort into a new feature. To avoid this from happening, we request that contributors create [an issue](https://github.com/onesine/react-tailwindcss-datepicker/issues) to first discuss any significant new features.
16
+
It's never a fun experience to have your pull request declined after investing a lot of time and
17
+
effort into a new feature. To avoid this from happening, we request that contributors create
18
+
[an issue](https://github.com/onesine/react-tailwindcss-datepicker/issues) to first discuss any
19
+
significant new features.
16
20
17
21
## Installation
18
22
@@ -24,8 +28,8 @@ yarn install
24
28
25
29
## Coding standards
26
30
27
-
We use `prettier` for making sure that the codebase is formatted consistently.
28
-
To automatically fix any style violations in your code, you can run:
31
+
We use `prettier` for making sure that the codebase is formatted consistently. To automatically fix
32
+
any style violations in your code, you can run:
29
33
30
34
**Using yarn**
31
35
@@ -61,16 +65,18 @@ npm dev
61
65
62
66
## Before you make a Pull Request
63
67
64
-
We recommend to run these scripts in sequence before you make your commit message amd open a Pull Request
68
+
We recommend to run these scripts in sequence before you make your commit message amd open a Pull
0 commit comments