File tree Expand file tree Collapse file tree 1 file changed +55
-0
lines changed Expand file tree Collapse file tree 1 file changed +55
-0
lines changed Original file line number Diff line number Diff line change
1
+ # Contribution Guide
2
+ This guide details the general rules to follow when working. Each project may have its own variation of this contribution guide.
3
+
4
+ > ** _ NOTE:_ ** Never push code directly to the organization repo
5
+
6
+ ## Initial Setup
7
+ 1 . Install git
8
+
9
+ 2 . Fork the project repo
10
+
11
+ 3 . Clone your fork on your local computer
12
+ ```
13
+ git clone https://github.com/<your-username>/<repository-name>.git
14
+ ```
15
+
16
+ 4 . Change working directory
17
+ ```
18
+ cd <repository-name>
19
+ ```
20
+
21
+ 5 . Add the upstream repository
22
+ ```
23
+ git remote add upstream https://github.com/VIZZ-WEB-SOLUTIONS/<repository-name>.git
24
+ ```
25
+
26
+ 6 . Now ` git remote -v ` should show 2 repositories.
27
+ - `origin` Your forked repository
28
+ - `upstream` Vizz Web Solutions Dev repository
29
+
30
+ 7 . install dependencies
31
+
32
+ ## Develop your contributions
33
+
34
+ 1 . Pull the latest changes
35
+ ```
36
+ git fetch --all
37
+ git pull --rebase upstream main
38
+ ```
39
+
40
+ 2 . Create a branch for the changes you want to work on rather than working off of your local main branch:
41
+ ```
42
+ // new branch name should relate to the features you are working on
43
+ git checkout -b <new-branch-name> upstream/main
44
+ ```
45
+
46
+ 3 . Write some code!
47
+
48
+ ## Submitting a pull request
49
+ 1 . git push -u origin ` <new-branch-name> `
50
+
51
+ 2 . In order to make the team aware of your changes, you can make a PR to the ` VIZZ-WEB-SOLUTIONS/<repository_name> ` repository from your fork.
52
+
53
+ 3 . Ask other team members to review the code.
54
+
55
+ 4 . Resolve all merge conflicts.
You can’t perform that action at this time.
0 commit comments