Add missing documentation on how to combine migrations in Django

[shmonks]

Dependency

• Missing information about how to combine migrations in Django

Overview

We need to make it easy to:

• Record any missing documentation about combining migrations in Django
• 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 Django. See Resource 1.01.
• This issue tracks the documentation that needs to be added for combining migrations in Django. 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 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 in GitHub and Django #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 #282 
- 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 combining Django migrations 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 combining Django migrations 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 docs: How to combine migrations before merging a PR #282

Section 2: List of comments/issues about missing documentation for combining Django migrations

• 2.01 Add missing documentation on how to combine migrations in Django #421 (comment)
  • 2.01.01 # [REPLACE WITH ISSUE NUMBER ONCE COMMENT IS MADE INTO ISSUE]
• 2.02 [REPLACE with link to your comment below]
  • 2.02.0x # [REPLACE WITH ISSUE NUMBER ONCE COMMENT IS MADE INTO ISSUE]

[shmonks]

Overview

We need to add a description of how to combine migrations in Django so that developers can integrate changes effectively. For example, if max_migration.txt is at 0027_... and you want to combine 0025_, 0026_, 0027_ into one.

Action Items

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

Resources/Instructions/Tags

• 1.01 docs: How to combine migrations before merging a PR #282
• 1.02 django

Documentation Addition Notes

What's missing?

• The process for combining migrations in Django is:

1. Roll back core app migrations to 0024

   ./scripts/migrate.sh core 0024

2. Delete unwanted migration files

   rm app/core/migrations/00{25,26,27}_*

3. Recreate max_migration.txt for core app

   docker-compose exec web python manage.py create_max_migration_files --recreate core
   # the file core/max_migration.txt should contain "0024_..."

4. Create combined migration file for core app

   ./script/migrate.sh core

Where should it go?

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

Where would this information have been useful?

• Many initial passes for PRs have multiple migration files that should really be a single Create Table migration

Which roles will benefit most from this information?

• Back end/Dev