Add missing documentation on how to add an alias in GitHub

[shmonks]

Dependency

• Information missing on how to add an alias in GitHub

Overview

We need to make it easy to:

• Record any missing documentation on how to add an alias in GitHub
• Keep those records in one place
• Create new issues based on those records

This issue is the place to record missing documentation and start creating related new issues.

Details

• We are striving to write documentation that helps developers use GitHub.
• This issue tracks the documentation that needs to be added on adding an alias in GitHub. If you've noticed missing documentation about other Git and/or Django processes,

see the following issues instead

• Add missing documentation to the PR review guide #419
• Add missing documentation on how to combine migrations in Django #421
• Add missing documentation on how to quickly checkout a PR #422
• Adding missing documentation on how to resolve migration conflicts #424
• Add missing documentation on how to apply changes from one file to another in GitHub #425

Action Items

• For each piece of missing information, copy and paste the following template into a new comment below.

### Overview
We need to add [REPLACE WITH WHAT NEEDS ADDING], so that developers can [REPLACE WITH BENEFIT]

### Action Items
- [ ] [REPLACE WITH ACTION ITEMS]

### Resources/Instructions/Tags 

- 1.0x [REPLACE WITH LINKS TO ANY EXTERNAL DOCS THAT MIGHT BE USEFUL (WITH INSTRUCTIONS, IF NEEDED)]
- 1.0x [REPLACE WITH ANY RELEVANT TAGS e.g., git, django, etc.]

### Documentation Addition Notes
#### What's missing?
[REPLACE WITH DESCRIPTION OF WHAT'S MISSING FROM THE DOCUMENTATION]
   
#### Where should it go?
[REPLACE WITH URL OR INDICATE NEW PAGE AND PARENT PAGE]

####  When would this information have been useful?
[REPLACE WITH LINK TO THE PR/ISSUE/SITUATION THAT PROMPTED THE NEED FOR THIS CHANGE/ADDITION]
   
#### Which roles will benefit most from this information?
[REPLACE WITH ROLES]

• Fill out as many of the template's fields as possible.
• Copy and paste a link to your comment in Section 2: List of comments/issues about missing documentation on adding an alias in GitHub below, using the next available number
• Copy the content of your comment
• Create a new issue, pasting the content of your comment into the new issue
• Add the following labels to the new issue
  • feature: docs: PD team documentation
  • size: 0.25pt
  • s: PD team
  • ready for dev lead
  • choose a complexity label that fits
  • choose the role label that fits
• When this new issue has been created, add a link to it in Section 2: List of comments/issues about missing documentation on adding an alias in GitHub below. Make sure the link to your new issue appears beneath the link to your comment, so we can ensure that all comments get made into issues
• Hide the original comment (you can mark it 'Resolved')

Section 2: List of comments/issues about missing documentation on adding an alias in GitHub

• 2.01 Missing Documentation on how to add an alias in Github #441

[shmonks]

Overview

We need to add documentation, so that developers can add a git alias to the global git config

Action Items

• Add content in the What's missing? section below to a new numbered item and linked page here: https://hackforla.github.io/peopledepot/contributing/howto/, editing or revising if necessary

Resources/Instructions/Tags

1.01 git

Documentation Addition Notes

What's missing?

This is the process for adding a git alias to the global git config:

1. Run this in the terminal:

   git config --global -e

2. That will open an editor in which you can edit the global git config file.

3. Add the git alias under the [alias] section and save the file. The alias is now available for use.

Where should it go?

[REPLACE WITH URL OR INDICATE NEW PAGE AND PARENT PAGE]

When would this information have been useful?

• Wherever documentation says to add a git alias

Which roles will benefit most from this information?

• Backend/Dev