Problem/Motivation
Follow up to #3607061: Don't spellcheck composer.json
In that issue, cspell config was updated so changes to composer.json files wouldn't cause failed builds. We removed some dictionary words that we no longer needed, but that caused cspell to fail in backport branches, as they still needed those words.
No one wants a backport to fail because of cspell. The spelling has already been checked when pipeline ran against main. It's a waste of develop time, and CI minutes.
Steps to reproduce
Proposed resolution
The simple approach is to just remove the cspell job from 11.x and 11.4.x, but that is not future proof. Instead we can take the same approach as #3580398: Skip on-commit jobs for the main and 11.x branches and add a condition on the job.
Remaining tasks
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
Issue fork drupal-3612933
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3612933-only-run-cspell-11.x
changes, plain diff MR !16422
- 3612933-only-run-cspell
changes, plain diff MR !16421
Comments
Comment #2
mstrelan commentedComment #5
mstrelan commentedComment #6
smustgrave commentedMakes sense, would love to see be able to automatically check for old words that don't need to be there. Like a warning, not failure, that words that can be removed are still there. But not sure if that's possible? Just speaking out loud. Know quietone will occasionally will update the dictionary of stale words.
Comment #9
longwaveI think we could re-output the dictionary files like we do with phpstan, then people can redownload them if they want? But none of this spelling stuff is critical really, although it's still good at catching silly typos.
Committed and pushed f7307570b3b to main and dfd362cef4e to 11.x. Thanks!
This could be backported further but not sure it's worth it now.