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
+32-11Lines changed: 32 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,17 +8,28 @@ Please note we have a [code of conduct](https://github.com/reactdeveloperske/rea
8
8
9
9
- Create a [new issue](https://github.com/reactdeveloperske/reactdevske-website/issues)
10
10
- Comment on the issue (if you'd like to be assigned to it) - that way the issue can be assigned to you.
11
+
12
+
### Open issues
13
+
- Go to [open issues](https://github.com/reactdeveloperske/reactdevske-website/issues)
14
+
- select an issue of your choice that is `open` or `need help` or is `up-for-grabs` and is not assigned.
15
+
- Comment on the issue (if you'd like to be assigned to it) - that way the issue can be assigned to you.
16
+
11
17
12
18
### Fork the repository (repo)
13
19
14
20
- If you're not sure, here's how to [fork the repo](https://help.github.com/en/articles/fork-a-repo)
15
21
16
22
17
-
### Set up your local environment (optional)
23
+
### Set up your local environment (optional)
18
24
19
25
If you're ready to contribute and create your PR, it will help to set up a local environment so you can see your changes.
20
26
21
-
1. Set up your development environment
27
+
1. Set up your development environment
28
+
- install your favorite text editor/IDE
29
+
- install [Nodejs](nodejs.org)
30
+
31
+
32
+
<br>
22
33
23
34
2. Clone your fork
24
35
@@ -49,37 +60,47 @@ $ git merge upstream/develop
49
60
50
61
3. Install dependencies
51
62
52
-
```
53
-
$ yarn
54
-
```
63
+
```
64
+
$ yarn install
65
+
```
55
66
or
56
67
57
68
```
58
69
$ npm install
59
70
```
71
+
<br>
72
+
73
+
### Make awesome changes!
74
+
75
+
<br>
76
+
60
77
61
-
### Make awesome changes!
62
78
63
79
1. Create new branch for your changes
64
80
65
81
```
66
82
$ git checkout -b new_branch_name
67
83
```
68
84
69
-
2.Start developing!
85
+
2.start development server
70
86
71
87
```
72
-
$ yarn start
88
+
$ yarn run dev
73
89
```
74
90
or
75
91
```
76
-
npm start
92
+
npm run dev
77
93
```
78
94
95
+
<br>
96
+
97
+
### Start developing!
98
+
<br>
99
+
79
100
- Open this directory in your favorite text editor / IDE, and see your changes live by visiting `localhost:3000` from your browser
80
101
- Pro Tip: Explore scripts within `package.json` for more build options
81
102
82
-
3. Commit and prepare for pull request (PR). In your PR commit message, reference the issue it resolves (see [how to link a commit message to an issue using a keyword](https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword).
103
+
1. Commit and prepare for pull request (PR). In your PR commit message, reference the issue it resolves (see [how to link a commit message to an issue using a keyword](https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword).
83
104
84
105
```
85
106
$ git commit -m "brief description of changes [Fixes #1234]"
- After your changes are commited to your GitHub fork, submit a pull request (PR) to the `develop` branch of the `reactdeveloperske/reactdevske-website` repo
97
118
- In your PR description, reference the issue it resolves (see [linking a pull request to an issue using a keyword](https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))
0 commit comments