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
Firstly, thank you for considering making a contribution to our project! It's people like you that make Operation Code such a great community.
4
-
5
-
We're an open source project and we love receiving contributions from our community - you! There are many ways to contribute to our projects, from writing tutorials or blog posts, improving documentation, submitting bug reports or feature requests, or writing code which can be merged into any of our repositories.
6
-
7
-
The team at Operation Code urges all contributors to join our Slack team. Participating in discussions with the community on our Slack channel, is the best way to run new ideas by the team, and is the best place to get help. You can get an invitation to our Slack channel by [requesting to join Operation Code](https://operationcode.org/join). Once in our Slack team, simply type: '/open #oc-python-projects' and then click enter. Feel free to ask for help; everyone is a beginner at first :smile_cat:!
8
-
9
-
**This guide assumes that you have some at least some familiarity with submitting a pull request on Github. If you don't, that's ok too though. Simply start by reading Github's own user documentation on how to fork a repository, and make your own edits. That documentation is [here](https://help.github.com/articles/about-pull-requests/) and [here](https://help.github.com/articles/creating-a-pull-request/). 3rd party tutorials on Git/Github can be found [here](https://medium.freecodecamp.org/what-is-git-and-how-to-use-it-c341b049ae61) and [here](https://medium.freecodecamp.org/how-to-use-git-efficiently-54320a236369?source=linkShare-e41cd5edcdac-1535829065)**
10
-
3
+
Firstly, thank you for considering making a contribution to our project! It's
4
+
people like you that make Operation Code such a great community.
5
+
6
+
We're an open source project and we love receiving contributions from our
7
+
community - you! There are many ways to contribute to our projects, from writing
8
+
tutorials or blog posts, improving documentation, submitting bug reports or
9
+
feature requests, or writing code which can be merged into any of our
10
+
repositories.
11
+
12
+
The team at Operation Code urges all contributors to join our Slack team.
13
+
Participating in discussions with the community on our Slack channel is the
14
+
best way to run new ideas by the team, and is the best place to get help. You
15
+
can get an invitation to our Slack channel by
16
+
[requesting to join Operation Code](https://operationcode.org/join). Once in our
17
+
Slack team, simply type: '/open #oc-python-projects' and then click enter. Feel
18
+
free to ask for help; everyone is a beginner at first :smile_cat:!
19
+
20
+
**This guide assumes that you have some at least some familiarity with
21
+
submitting a pull request on Github. If you don't, that's ok too. Simply
22
+
start by reading Github's own user documentation on how to fork a repository,
23
+
and make your own edits. That documentation is
24
+
[here](https://help.github.com/articles/about-pull-requests/) and
25
+
[here](https://help.github.com/articles/creating-a-pull-request/). 3rd party
@@ -37,31 +97,41 @@ To work on the codebase for this project, you will need to have those dependenci
37
97
<details>
38
98
<summary>Click to Expand</summary>
39
99
40
-
* After forking this repository to your own github account, and cloning it to your dev environment, you can now create a new branch on your machine. It's wise to name this branch, after the issue you are trying to fix, or the feature you are trying to add.
100
+
- After forking this repository to your own github account, and cloning it to
101
+
your dev environment, you can now create a new branch on your machine. It's
102
+
wise to name this branch after the issue you are trying to fix or the
103
+
feature you are trying to add.
41
104
42
-
```bash
43
-
git checkout -b creatingContributionGuide
44
-
```
105
+
```bash
106
+
git checkout -b creatingContributionGuide
107
+
```
45
108
46
-
* In the example above, I have created a new branch, named "creatingContributionGuide". This command also "checks out" the branch, meaning git now knows that is the branch you are working on. You can check what branch you are working on by using the `branch` command.
109
+
- In the example above, I have created a new branch, named
110
+
"creatingContributionGuide". This command also "checks out" the branch,
111
+
meaning git now knows that is the branch you are working on. You can check
112
+
what branch you are working on by using the `branch` command.
47
113
48
-
```bash
49
-
git branch
50
-
```
51
-
* Following my example, `git branch`, would output "creatingContributionGuide" in my terminal.
114
+
```bash
115
+
git branch
116
+
```
52
117
53
-
* Once you have finished working on your issue, push your changes to your own github repo, and then submit a pull request.
118
+
- Following my example, `git branch`, would output "creatingContributionGuide"
119
+
in my terminal.
54
120
55
-
* To return to your main `master` branch, type the following command in your terminal.
121
+
- Once you have finished working on your issue, push your changes to your own
122
+
github repo, and then submit a pull request.
56
123
57
-
```bash
58
-
git checkout master
59
-
```
60
-
</details>
124
+
- To return to your main `master` branch, type the following command in your
0 commit comments