github-pages-javascript-prototype VS pyspelling

I had an older repository from a prototype I did and it contained some JavaScript and HTML. After some experimentation, I got the configuration working for checking the spelling of JavaScript and a HTML files.

Which resulted in updates to several of the dependencies used by the core component PySpelling.

GitHub Actions are convenience for packaging tooling for execution on the GitHub platform or using a local runner etc. As you can see on the GitHub Marketplace this mean that a lot of actions are wrapping of common and useful tools to adapt to the GitHub toolbox and toolchain. The same goes for GitHub Spellcheck Actions, it is an implementation based on PySpelling a nifty tool to do spelling checks on Python, Markdown, Text files etc.

Over the summer PySpelling has been updated to version 2.8, due to minor issue it was swiftly followed by 2.8.1. See the release history for PySpelling

Now we have to add a configuration file for the spelling checker. It uses PySpelling under the hood. When checking Markdown files, it first converts a Markdown text file's buffer using Python Markdown and returns a single SourceText object containing the text as HTML. Then it captures the HTML content, comments, and even attributes and performs the check. It has a lot of configuration options, but here we are going to see only an example with some basics. For further info you can read the docs of the rojopolis/spellcheck-github-actions Github action.

Additionally issue #53 was addressed, it describes an issue with ignoring Markdown regions with code fences. This however was an upstream issues in pyspelling the core component in this action. The maintainer of pyspelling was to fix it. So the requirement for pyspelling in the action was bumped from 2.6.1 to 2.7.3.