Add missing documentation to the PR review guide

[shmonks]

Dependency

• Information missing from the PR review guide

Overview

We need to make it easy to:

• Record any missing documentation for the PR review guide
• 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 create and review PRs. See Resource 1.01
• This issue tracks the documentation that needs to be added to the PR review guide. If you've noticed missing documentation about other Git and/or Django processes,

see the following issues instead

• Add missing documentation on how to combine migrations in Django #421
• Add missing documentation on how to quickly checkout a PR #422
• Add missing documentation on how to add an alias in GitHub #423
• 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.01 Example of another team's PR review guide [Website team's PR review guide](https://github.com/hackforla/website/wiki/How-to-review-pull-requests)
- 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 for PR Review guide 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 for PR Review guide 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')

Resources/Instructions

• 1.01 Example of another team's PR review guide Website team's PR review guide

Section 2: List of comments/issues about missing documentation for PR Review guide

• 2.01 Missing Documentation for the PR Review Guide #438

[shmonks]

Overview

We need to create a list of common things to look out for when doing a PR review, so that developers can catch things which can often be missing/wrong

Action Items

• Create a new numbered item called 'Review a GitHub Pull Request (PR)' on this page: https://hackforla.github.io/peopledepot/contributing/howto/
• Create a new page with that title, and add the following items under the heading 'Common things to look out for when reviewing a pull request':
  • PR destination should be peopledepot/main
  • Check model fields
  • Names should be reasonable
  • FK relations should drop the ending _id when going from DB to Django notation
  • Some fields already provided by AbstractBaseModel should not be added
• Insert hyperlink from the numbered item on this page to the new page you created

Resources/Instructions/Tags

1.01 Example of another team's PR review guide Website team's PR review guide
1.02 git

Documentation Additional Notes

Where would this information have been useful?

• Create table project_program_area_xref #376 (review)

Which roles will benefit most from this information?

• Backend/Dev
• DB Architect