Replace `Github` with `GitHub` in CONTRIBUTING.md Section 1.4

[daras-cu]

Prerequisite

1. Be a member of Hack for LA. (There are no fees to join). If you have not joined yet, please follow the steps on our Getting Started page and attend an onboarding session.
2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

We need to replace instances of Github and github with GitHub so that we display the company name correctly.

Action Items

• In your local IDE, navigate to CONTRIBUTING.md
• In section 1.4.b, replace

Verify that your local cloned repository is pointing to the correct `origin` URL (that is, the forked repo on your own Github account):

with

Verify that your local cloned repository is pointing to the correct `origin` URL (that is, the forked repo on your own GitHub account):

• In section 1.4.c, replace

#### **1.4.c What if you accidentally cloned using the repository URL from the HackForLA Github (instead of the fork on your Github)?**

with

#### **1.4.c What if you accidentally cloned using the repository URL from the HackForLA GitHub (instead of the fork on your GitHub)?**

*Note there are two instances of Github that need to be corrected to GitHub in the above line

• In section 1.4.c, replace

Set your forked repo on your Github as an `origin` remote:

with

Set your forked repo on your GitHub as an `origin` remote:

• With CONTRIBUTING.md still open, make a note of the section in which the replaced content appears, so that you will know where to look in the document to preview the change.
• Changes to CONTRIBUTING.md cannot be tested locally, rather they must be tested after pushing the issue branch to your fork of the repository. Push your issue branch in the usual manner, but before creating the Pull Request, check your updates using this test URL. Also store the test URL for use in a later step:

https://github.com/[REPLACE WITH GITHUB HANDLE]/website/blob/[REPLACE WITH NAME OF ISSUE BRANCH]/CONTRIBUTING.md

(for example: https://github.com/bonniewolfe/website/blob/issue-branch-1234/CONTRIBUTING.md)

• Create a pull request with your changes. In the Pull Request, after the "Why did you make the changes" section, add this line to help reviewers, replacing the text in brackets (and the brackets) with the test URL from the previous Action Item.

For Reviewers: Do not review changes locally, rather, review changes at [REPLACE WITH TEST URL]

Resources/Instructions

• CONTRIBUTING.md
• Getting started with writing and formatting on GitHub
• This issue resulted from ER: Find all the places that Github should be GitHub and fix #6161

Merge Team

• After closing this issue, check off the dependency in ER: Find all the places that Github should be GitHub and fix #6161. If all dependencies have been completed, close ER: Find all the places that Github should be GitHub and fix #6161

[HackforLABot]

Hello @katiejnete, we appreciate you taking on issue #7439, however it looks like you've already worked on enough issues of this complexity. Try checking out some of the issues of the next complexity from the Prioritized Backlog :)

We are going to unassign you from this issue so you can take on another issue.

Hfla appreciates you! :)

P.S. There is one exception to this rule/automation, and that is if you were away for a long time, and need to do the issue ladder again. If that is the case, please post the following note on the issue and on your Skills Issue (Pre-work Checklist). A Merge team member will reassign you to this issue, and will help you get assigned to subsequent issues up to medium size.

I am returning after a significant time away, and need to do the issue ladder again. Please assign me back to this issue.