Approver Guide Documentation

[jjnether]

Description

Add a page for approvers to the docs.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 24.56%. Comparing base (e130d15) to head (d3bb952).

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #4373       +/-   ##
===========================================
- Coverage   89.88%   24.56%   -65.32%     
===========================================
  Files           1        1               
  Lines         346      346               
===========================================
- Hits          311       85      -226     
- Misses         35      261      +226     

see 1 file with indirect coverage changes