Create issue template "Resolve Spell Check warning"

[roslynwythe]

Dependency

• Create wiki page "How to manage spell check warnings" #6519
• Epic: Create issues to add false positives to cspell.json #5312

Overview

We need a template for reporting spell check warnings, so that we can create issues to address.

Action Items

• Create a new file .github/ISSUE_TEMPLATE/spellcheck-warning.md
• Copy/Paste the text below into the file, then save it
• Refer to the instructions for testing the new template and preparing the Pull Request. ¹

Content of issue template

---
name: Resolve spell check warning
about: For reporting spell check warnings ("unknown word")
title: 'Resolve spell check warning(s) in: [replace with file path] '
labels: 'good first issue, feature: spelling, role: back end/devOps , size: 0.25pt'
assignees: ''

---

### Overview
We need to manage the warnings ("unknown word") generated by spell check

### Action Items
- [ ] Open the file `[REPLACE WITH FILE PATH]` in your IDE
- [ ] Refer to instructions on "How to manage spell check warnings" (resource 1)
- [ ] Copy the block "Resolving spell check warnings" into a new comment in this issue, then select the green Comment button to create the comment. Follow the instructions in the comment you just created.

### Resources/Instructions
1. [draft: How to manage spell check warnings](https://github.com/hackforla/website/issues/6519#issuecomment-2021279777)
2. [Code Spell Checker](https://streetsidesoftware.com/vscode-spell-checker/)
3. [Introduction to JSON](https://www.json.org/json-en.html)
---

Resources

Footnotes

1. Testing issue templates instructions ↩

[github-actions]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels