<commit_before># GitHub and Markdown

[GitHub](https://help.github.com/categories/writing-on-github/) acts as a source code management system for Open Learning Exchange. It's a very simple open source system that is easy to learn and to use. Please read some of the basic instructions below as a user manual for OLE on GitHub. 

[Markdown Wiki](http://dynalon.github.io/mdwiki/#!quickstart.md) is the software you're currently reading on that OLE uses for our Virtual intern program. Markdown (MD) Wiki allows us to use Markdown and javascript on GitHub so that it is easily compatible with our current development environment. To be explicit, Markdown is a simplified development language which allows you to format and write text. 
Below is a screenshot of what Markdown language with a preview looks like: 

![Markdown Preview](/ll_CC/pages/uploads/images/markdown.png)

Below is a cheat sheet of Markdown so you can have more information on writing MD on your individual Markdown Wiki pages:

![Markdown Cheat Sheet](/ll_CC/pages/uploads/images/Markdown_Reference.png)

The main GitHub page devoted to this is found at [open-learning-exchange/open-learning-exchange.github.io](https://github.com/open-learning-exchange/open-learning-exchange.github.io) and our virtual interns will essentially create their own Markdown Wiki page as a copy of open-learning-exchange.github.io. Please find the steps below to do this after a brief description of GitHub and its functionality. 

As you have already created a username on GitHub, we can assume that you understand the basic layout and functionality. Please explore and do some basic googling if not. On GitHub, it's important to always be sure that you are working on your own GitHub page if you're editing (which you can tell based off of the name before the slash and the repositority after the slash: ex. EmilyLarkin/BeLL-Apps). All of Open Learning Exchange's work can be [found here](https://github.com/open-learning-exchange). All of the different repositories represent differnt types of software used by OLE and the repositories act as categorizing system. 

There is a lot of GitHub to learn, but to acclimatize you to it, we will provide a basic example of how to change something on GitHub. This example with specifically create your own <username>.github.io and allow you to edit and commit your changes. 

First, you will need to find the correct GitHub repository to fork. Forking is essentially creating a copy on your own user so that you don't edit or mess up the main file. To make it easier on you, I will provide you with a link to the correct repository [here](https://github.com/open-learning-exchange/open-learning-exchange.github.io). 
Now you will fork the repository to your own page. Look at the picture below to find the fork button. 

![Forking on GitHub](/ll_CC/pages/uploads/images/Forking on GitHub.png)

After your fork it, you will be on your page: <username>/open-learning-exchange.github.io. Then go to settings at the top middle of the page and rename your repository to your name. See example below. 

![Renaming Repository](/ll_CC/pages/uploads/images/Rename Repository.png)

Once again, it's important to distinguish now the difference between your personal GitHub account and the Open Learning Exchange account. As we want to keep a 'clean' version of code, everyone forks repositories and then saves them back for approval (called a pull request) before the Open Learning Exchange code is updated. Be sure to ALWAYS work on your personal account via forking and pull requests. 

Now, you can edit your files and check out our <username>.github.io in a web browser. To edit, click on the `II_CC` folder and then click on `pages` folder. Then, click `New File` and make the filename the exact same name as your gitter.im username (minus the @). I have created pages for you using your gitter.im chat name so it's important you stick with that name. For reference, my link to this page is EmilyLarkin.github.io/ll_CC/pages/EmilyLarkin.md and yours should look similar in a parallel format. 

From this, click the pencil icon to edit (as shown below) and type your name, your location/time zone, and OS. Then scroll down to the bottom of the page and click `Commit Changes`. 

![Edit](/ll_CC/pages/uploads/images/Edit.png)

Now check what this looks like on your own page (<username>.github.io/ll_CC/#!pages/<username>.md). Check and double check that everything looks good and is working before initiating a pull request. 

Then, you can create a pull request by clicking the `Pull requests` button and then clicking `New pull request`. Then click `Create pull request` and someone from our team will then merge and allow your pull request once everything looks good. After the pull request is completed, you'll be able to see this on open-learning-exchange.github.io in addition to your personal page. Let us know when you have completed this step in the [gitter.im chat](https://gitter.im/open-learning-exchange/chat).
<commit_msg>Update githubandmarkdown.md<commit_after># GitHub and Markdown

[GitHub](https://help.github.com/categories/writing-on-github/) acts as a source code management system for Open Learning Exchange. It's a very simple open source system that is easy to learn and to use. Please read some of the basic instructions below as a user manual for OLE on GitHub. 

[Markdown Wiki](http://dynalon.github.io/mdwiki/#!quickstart.md) is the software you're currently reading on that OLE uses for our Virtual intern program. Markdown (MD) Wiki allows us to use Markdown and javascript on GitHub so that it is easily compatible with our current development environment. To be explicit, Markdown is a simplified development language which allows you to format and write text. 
Below is a screenshot of what Markdown language with a preview looks like: 

![Markdown Preview](/ll_CC/pages/uploads/images/markdown.png)

Below is a cheat sheet of Markdown so you can have more information on writing MD on your individual Markdown Wiki pages:

![Markdown Cheat Sheet](/ll_CC/pages/uploads/images/Markdown_Reference.png)

The main GitHub page devoted to this is found at [open-learning-exchange/open-learning-exchange.github.io](https://github.com/open-learning-exchange/open-learning-exchange.github.io) and our virtual interns will essentially create their own Markdown Wiki page as a copy of open-learning-exchange.github.io. Please find the steps below to do this after a brief description of GitHub and its functionality. 

As you have already created a username on GitHub, we can assume that you understand the basic layout and functionality. Please explore and do some basic googling if not. On GitHub, it's important to always be sure that you are working on your own GitHub page if you're editing (which you can tell based off of the name before the slash and the repositority after the slash: ex. EmilyLarkin/BeLL-Apps). All of Open Learning Exchange's work can be [found here](https://github.com/open-learning-exchange). All of the different repositories represent differnt types of software used by OLE and the repositories act as categorizing system. 

There is a lot of GitHub to learn, but to acclimatize you to it, we will provide a basic example of how to change something on GitHub. This example with specifically create your own <username>.github.io and allow you to edit and commit your changes. 

First, you will need to find the correct GitHub repository to fork. Forking is essentially creating a copy on your own user so that you don't edit or mess up the main file. To make it easier on you, I will provide you with a link to the correct repository [here](https://github.com/open-learning-exchange/open-learning-exchange.github.io). 
Now you will fork the repository to your own page. Look at the picture below to find the fork button. 

![Forking on GitHub](/ll_CC/pages/uploads/images/Forking on GitHub.png)

After your fork it, you will be on your page: username/open-learning-exchange.github.io. Then go to settings at the top middle of the page and rename your repository to your name. See example below. 

![Renaming Repository](/ll_CC/pages/uploads/images/Rename Repository.png)

Once again, it's important to distinguish now the difference between your personal GitHub account and the Open Learning Exchange account. As we want to keep a 'clean' version of code, everyone forks repositories and then saves them back for approval (called a pull request) before the Open Learning Exchange code is updated. Be sure to ALWAYS work on your personal account via forking and pull requests. 

Now, you can edit your files and check out your username.github.io in a web browser. To edit, click on the `II_CC` folder and then click on `pages` folder. Then, click `New File` and make the filename the exact same name as your gitter.im username (minus the @). I have created pages for you using your gitter.im chat name so it's important you stick with that name. For reference, my link to this page is EmilyLarkin.github.io/ll_CC/pages/EmilyLarkin.md and yours should look similar in a parallel format. 

From this, click the pencil icon to edit (as shown below) and type your name, your location/time zone, and OS (including version). Feel free to add a short description of yourself as well so your fellow virtual interns know who you are. Then scroll down to the bottom of the page and click `Commit Changes`. 

![Edit](/ll_CC/pages/uploads/images/Edit.png)

Now check what this looks like on your own page (username.github.io/ll_CC/#!pages/username.md). Check and double check that everything looks good and is working before initiating a pull request. 

Then, you can create a pull request by clicking the `Pull requests` button and then clicking `New pull request`. Then click `Create pull request` and someone from our team will then merge and allow your pull request once everything looks good. After the pull request is completed, you'll be able to see this on open-learning-exchange.github.io in addition to your personal page. Let us know when you have completed this step in the [gitter.im chat](https://gitter.im/open-learning-exchange/chat).

{'fraction_non_alphanumeric': 0.0579624717555752, 'fraction_numerical': 0.0, 'mean_word_length': 4.44385026737968, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 9, 'https://': 10, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2468813', 'n_tokens_mistral': 2637, 'n_tokens_neox': 2477, 'n_words': 1477}