-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathCONTRIBUTING
58 lines (40 loc) · 2.52 KB
/
CONTRIBUTING
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
# Contributing to E-commerce Backend
We would love for you to contribute to E-commerce Backend, help make it even better than it is today!
As a contributor, here are the guidelines we would like you to follow:
- [Issues and Bugs](#issue)
- [Submission Pull Request](#submit-pr)
- [Managing Labels](#managing-labels)
- [Other References](#other-references)
## <a name="issue"></a> Found a Bug?
If you find a bug in the source code, You can <a href="https://github.com/Alwisteins/e-commerce-model/issues">Submit an issue</a> to e-commerce-model Repository.
## <a name="submit-pr"></a> Submitting a Pull Request (PR)
Before you submit your Pull Request (PR) consider the following guidelines:
1. Search [GitHub](https://github.com/Alwisteins/e-commerce-model/pulls) for an open or closed PR that relates to your submission.
2. Fork `Alwisteins/e-commerce-model`, do not fork if you a collaborator
3. Clone it to your local system
```shell
git clone https://github.com/Alwisteins/e-commerce-model.git
```
or you can use SSH to clone this repository instead of using https
```shell
git clone [email protected]:Alwisteins/e-commerce-model.git
```
4. Make a new branch to your pull request
```js
git branch <feat/features_name>
// or create new branch with change branch
git checkout -b <feat/features_name>
```
5. Make your changes
6. Push it back to your repo, if you a collabolators in this project just clone and do not fork it
7. Click the Compare & pull request button
8. Click Create pull request to open a new pull request
Congratulations, you have contributed to the E-commerce Backend project, just waiting for a response from the owner of this repository.
## <a name="managing-labels"></a> Managing labels
You can manage your work on GitHub by creating labels to categorize issues, pull requests, and discussions. [More about github labels](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels).
## <a name="other-references"></a> Other References
- https://github.blog/2013-05-14-closing-issues-via-pull-requests/
- https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue
- https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
- https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork
- https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork