Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add codespell: config, workflow and have typos fixed #770

Closed
wants to merge 6 commits into from

Conversation

yarikoptic
Copy link
Contributor

workflow would only detect when a new typo is introduced, it will not automagically inject its fix somehow.

more info on codespell: https://github.com/codespell-project/codespell

=== Do not change lines below ===
{
 "chain": [],
 "cmd": "codespell -w",
 "exit": 0,
 "extra_inputs": [],
 "inputs": [],
 "outputs": [],
 "pwd": "."
}
^^^ Do not change lines above ^^^
@VisLab
Copy link
Member

VisLab commented Oct 1, 2023

@yarikoptic Thanks for the suggestion. I am worried about the "fixing typo automagically" on the first round. There are a number of items where a spell check change would be unfortunate. I haven't used this before. Is there a way to not do the automagically on the first round to see where the dust falls? I'd like to put this on all our repos.

@yarikoptic
Copy link
Contributor Author

It doesn't fix anything automatically unless you ask it. Workflow just fails if typo is added, then you fix it or add to skips in configuration and continue

@yarikoptic
Copy link
Contributor Author

Here is the adhoc script https://github.com/yarikoptic/improveit/blob/main/codespellit I used to add codespell here. I guess it could be organization wide workflow which would just check if project has codespell config to proceed, and then each repo would need similar pr fixing initial set of typos

@VisLab
Copy link
Member

VisLab commented Oct 2, 2023

@yarikoptic unfortunately we're going to have to revert all of the codespell related commits as they changed the hed schema files which must not be changed regardless of typos. I didn't notice it until I did the merges and then @IanCa pointed it out.

This is going to take some work to do all of the proper excludes.

@yarikoptic
Copy link
Contributor Author

It is easy to exclude files. What files should I exclude?

@VisLab
Copy link
Member

VisLab commented Oct 2, 2023 via email

@VisLab
Copy link
Member

VisLab commented Oct 17, 2023

@yarikoptic - we fixed some of the exclusions and put your suggestions in another PR. Thx.

@VisLab VisLab closed this Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants