• List changes with brief descriptions
  • Closes #

Submitter Checklist

• Verify all tests pass
  • Run tests with docker-compose -f test-compose.yml -p onitest up test
• Update README.md and docs/ as necessary
  • If a manage.py command is added, deleted, or modified its help text must
    be valid and it should be documented in detail in
    docs/advanced/admin-commands.md
• Copy the changelog file template in changelogs/ to a new file in the
  same directory named following the YYYY-MM-DD-branch_name.md pattern with
  the day's date and your branch name
  • Describe change(s) in appropriate section(s)
  • List self in Contributors section
• If a release PR:
  • Move changelog files' contents from changelogs/ to CHANGELOG.md
    • Delete files after contents moved to new release in CHANGELOG.md
  • Update core/version.py with new version
• Resolve merge conflicts
• @mention individual(s) you would like to review the PR
  • Reviews for releases must come from a reviewer at another institution

Reviewer Checklist

• Verify all tests pass
• Review changes for behavior, bugs, and compliance with Development
  Standards
  • Request the submitter make any changes rather than pushing changes yourself.
    Otherwise ask another reviewer to look at any changes you have made.
• If a release, follow the Release
  Checklist