Set up a basic CI workflow #7

New issue

Open

opened 2025-10-08 00:09:19 -03:00 by dunossauro · 1 comment

dunossauro commented

2025-10-08 00:09:19 -03:00

Member

Since we already have the static checking structure and the setup to run tests (even though tests don't exist yet), we can create a simple workflow using Forgejo Actions to validate the following:

typos: Check for spelling errors in the code.
lint: Ensure adherence to code style standards.
test: Run tests (once they are available).

Although we don't have a dedicated typo tool yet, setting one up is relatively simple. My recommendation is to use typos. The reason for this is that most of us are non-native English speakers, so spelling mistakes or strange word choices might occur more frequently in the code.

Since we already have the static checking structure and the setup to run tests (even though tests don't exist yet), we can create a simple workflow using [Forgejo Actions](https://forgejo.org/docs/latest/user/actions/reference/) to validate the following: * **typos:** Check for spelling errors in the code. * **lint:** Ensure adherence to code style standards. * **test:** Run tests (once they are available). Although we don't have a dedicated typo tool yet, setting one up is relatively simple. My recommendation is to use [**typos**](https://github.com/crate-ci/typos). The reason for this is that most of us are non-native English speakers, so spelling mistakes or strange word choices might occur more frequently in the code.