Added guideline for no themes from opening sequences
Description
Added a guideline for themes to not be from opening sequences.
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)
[x] 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.
Merging #2036 (26e7bce) into master (ceab515) will decrease coverage by 67.20%.
Report is 14 commits behind head on master.
The diff coverage is 25.00%.
Added guideline for no themes from opening sequences
Description
Added a guideline for themes to not be from opening sequences.
Screenshot
Issues Fixed or Closed
Type of Change
.github/...
)Checklist
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.