Add codespell: config, github workflow + make it fix some typos #1430
Conversation
|
|
|
@yarikoptic - We do have spell-checking enabled already (see https://github.com/USRSE/usrse.github.io/blob/main/.github/workflows/linting.yaml#L17). Why should we switch to this one? |
|
oh right ! and that is the one which uses codespell dictionary. It is strange then (worth investigation by someone interested) why if someone approves CI run, we might see/compare both |
Could it be because the |
|
dunno -- not familiar with |
|
It's not the spaces. I checked the workflow logs and even tested it out in my own container, and it runs as specified despite not finding the actual typos. Weird. I'd like to keep digging a bit more. |
| @@ -30,7 +30,7 @@ place **Friday, March 11th at 11AM Pacific/ 2PM Eastern / 7PM GMT** | |||
|
|
|||
| ### Abstract | |||
|
|
|||
| The role of a Research Software Engineer (RSE) is to transform research concepts and methods into practical computing workflows, blending established and innovative software techniques that incorporate technical sustainability and excellence. But to tread this path successfully it takes allies, collaborators, and process repeatability to make things happen. So how does an RSE build up this kind of ecosystem of success? This talk details how you can develop a diverse pool of resources and how sometimes reaching outside of the task you’ve been given can result in the breakthrough you need. | |||
There was a problem hiding this comment.
"tread" seems correct to me here, not "thread".
There was a problem hiding this comment.
indeed... dang rare word. thanks! fixed (ignored/redone fixing)
=== Do not change lines below ===
{
"chain": [],
"cmd": "codespell -w -i 3 -C 2",
"exit": 0,
"extra_inputs": [],
"inputs": [],
"outputs": [],
"pwd": "."
}
^^^ Do not change lines above ^^^
=== Do not change lines below ===
{
"chain": [],
"cmd": "codespell -w",
"exit": 0,
"extra_inputs": [],
"inputs": [],
"outputs": [],
"pwd": "."
}
^^^ Do not change lines above ^^^
yarikoptic
force-pushed
the
enh-codespell
branch
from
8a9268a
to
a5b5f5d
Compare
Description
I am on the quest to make the world the typo free place ;)
Workflow would just detect typos, not fix them
Checklist:
I have completed any content reviews, such as getting input from relevant working groups. If no, please note this and wait to post the PR to the #website channel until the content has been settled.-- i do not think it is applicable