Develop GHA for spell checking PRs

[roslynwythe]

Dependency

• 5312

Overview

We need a GHA to scan the files changed in Pull Requests using the Code Spell Checker CLI, in order to ensure that no misspellings are posted on the website.

Action Items

• [ ] Become familiar with the resources describing the HfLA GHA archtecture[^1] and testing procedures[^2]
• [ ] Utilitize the Code Spell Checker CLI[^3] within a GitHub action, to be triggered when Pull Requests are opened (merging into gh-pages)
• [ ]

Resources/Instructions

UI for failed spell check


Adding spell checking to my blog's build process [^1]:Hack for LA's GitHub Actions [^2]:HfLA GitHub Actions [^3]:Code Spell Checker npm package installation [^4]:How to set up cspell for spelling mistake free code

[github-actions[bot]]

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

NOTE: Please ignore the adding proper labels 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

[ExperimentsInHonesty]

• should we wait until all the false positives are added to cspell.json https://github.com/hackforla/website/issues/5312 before we do this issue?