You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to create an issue to discuss with the maintainers of this repo before I went ahead and deleted a test, but it appears this project is using both a Pre-Commit hook called file-contents-sorter and a test called test_dictionary_sorting() to enforce dictionaries have been sorted.
If I'm not missing anything, since Pre-Commit is enforced as a CI check before merge, the test_dictionary_sorting() test can be deleted. If that's accurate, I can get a PR in deleting the test.
Truth be told, I'm not really following what they're trying to say. Are we sure they were aware that Pre-Commit is enforced as a CI check? From what I can tell, there's really no need to have both.
Activity
DimitriPapadopoulos commentedon Feb 16, 2024
Both were added in #2973. I think the explanation is in a comment:
Can you have a look?
korverdev commentedon Feb 17, 2024
Truth be told, I'm not really following what they're trying to say. Are we sure they were aware that Pre-Commit is enforced as a CI check? From what I can tell, there's really no need to have both.
DimitriPapadopoulos commentedon Feb 18, 2024
The Makefile distinguishes between
check-dictionariesimplemented in actual tests:codespell/Makefile
Lines 13 to 21 in edef040
and
sort-dictionariesimplemented using pre-commit:codespell/Makefile
Lines 27 to 28 in edef040