Add codespell support (config, workflow to detect/not fix) and make it fix few typos #603
Conversation
…(but ignoring overall fail due to ambigous ones)
=== Do not change lines below ===
{
"chain": [],
"cmd": "codespell -w || :",
"exit": 0,
"extra_inputs": [],
"inputs": [],
"outputs": [],
"pwd": "."
}
^^^ Do not change lines above ^^^
=== 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 ^^^
|
Dear @yarikoptic , Thank you for your interest in siibra-python. We are in the middle of a large refactor at the moment. I would imagine your PR would almost certainly cause merge conflicts. We understand your time is precious, and would thus like to offer to implement codespell once refactor is stable, and attribute you as a co-contributor[1]. If you would prefer to create new PR/commits once refactor becomes stable, we can also offer to ping you when that is the case (if this is the case, please let us know in this issue). In either case, we will keep this PR open until it is resolved in one of the two ways above. |
|
Whatever works for you. Ping be whenever |
|
Dear @yarikoptic, |
|
coolio. |
Again, great talk at INCF 2024 @dickscheid ! Amazing scale of endeavors. Need to try siibra-python and see how we could integrate your online options with our external servicing for https://dandiarchive.org/ . Let's chat more while in the same room ;)
Meanwhile - my humble contribution to siibra is this PR.
More about codespell: https://github.com/codespell-project/codespell .
I personally introduced it to dozens if not hundreds of projects already and so far only positive feedback.
CI workflow has 'permissions' set only to 'read' so also should be safe.