From 50e81a1a61cdbe6a9538fd1ffd4253b31b0d1854 Mon Sep 17 00:00:00 2001 From: Yaroslav Halchenko Date: Thu, 6 Apr 2023 10:29:50 -0400 Subject: [PATCH 1/4] Add github action to codespell master on push and PRs --- .github/workflows/codespell.yml | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 .github/workflows/codespell.yml diff --git a/.github/workflows/codespell.yml b/.github/workflows/codespell.yml new file mode 100644 index 0000000..5768d7c --- /dev/null +++ b/.github/workflows/codespell.yml @@ -0,0 +1,19 @@ +--- +name: Codespell + +on: + push: + branches: [master] + pull_request: + branches: [master] + +jobs: + codespell: + name: Check for spelling errors + runs-on: ubuntu-latest + + steps: + - name: Checkout + uses: actions/checkout@v3 + - name: Codespell + uses: codespell-project/actions-codespell@v1 From 9f20049a800f59042dc202d9b7ff71269fdfed58 Mon Sep 17 00:00:00 2001 From: Yaroslav Halchenko Date: Thu, 6 Apr 2023 10:29:50 -0400 Subject: [PATCH 2/4] Add rudimentary .codespellrc --- .codespellrc | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 .codespellrc diff --git a/.codespellrc b/.codespellrc new file mode 100644 index 0000000..5aa4b5e --- /dev/null +++ b/.codespellrc @@ -0,0 +1,3 @@ +[codespell] +skip = .git,*.pdf,*.svg +# ignore-words-list = From 56a273f6ec9d535ef4e2ae5391901ca8aab84dfa Mon Sep 17 00:00:00 2001 From: Yaroslav Halchenko Date: Thu, 6 Apr 2023 10:30:18 -0400 Subject: [PATCH 3/4] [DATALAD RUNCMD] one ambigous typo fix === Do not change lines below === { "chain": [], "cmd": "git-sedi achive achieve", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 48fe5b5..3a53255 100644 --- a/README.md +++ b/README.md @@ -959,7 +959,7 @@ user@localhost:~/bats-file$ vagrant up The line above spins up a brand new virtualbox image and provisions with prerequisites. -However, as the tests require not to be on a network share due to running commands eg: `mknod`, the files are shared into the VM by `rsync` module. Rsync in vagrant only runs initialy and stops. During the active development, you regularly change files and might want to see the impact. To achive that, you have to use auto rsync. +However, as the tests require not to be on a network share due to running commands eg: `mknod`, the files are shared into the VM by `rsync` module. Rsync in vagrant only runs initialy and stops. During the active development, you regularly change files and might want to see the impact. To achieve that, you have to use auto rsync. > `auto-rsync` is a long running command. It means that it has to run on terminal screen as long as the VM is up and running. So, you have to keep this in a dedicated terminal screen. From 4719b19b47114f878bf78d7288bc421925a38aba Mon Sep 17 00:00:00 2001 From: Yaroslav Halchenko Date: Thu, 6 Apr 2023 10:30:22 -0400 Subject: [PATCH 4/4] [DATALAD RUNCMD] run codespell throughout === Do not change lines below === { "chain": [], "cmd": "codespell -w", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 3a53255..7e369df 100644 --- a/README.md +++ b/README.md @@ -825,7 +825,7 @@ error message on the standard error. ``` -- ERROR: temp_make -- -mktemp: failed to create directory via template ‘/etc/samle.bats-1-XXXXXXXXXX’: Permission denied +mktemp: failed to create directory via template ‘/etc/sample.bats-1-XXXXXXXXXX’: Permission denied -- ``` @@ -866,7 +866,7 @@ error message on the standard error. ``` -- ERROR: temp_del -- -rm: cannot remove '/etc/samle.bats-1-04RUVmBP7x': No such file or directory +rm: cannot remove '/etc/sample.bats-1-04RUVmBP7x': No such file or directory -- ``` @@ -949,7 +949,7 @@ path : /path/to/non-existent-file ## **Development** -No one would want to develop piece of bash dependant libraries on their laptops due to single mistake (globbing for instance) can cause a disaster. In order to prevent this there is a Vagrantfile that you can use. +No one would want to develop piece of bash dependent libraries on their laptops due to single mistake (globbing for instance) can cause a disaster. In order to prevent this there is a Vagrantfile that you can use. In order to start development environment, you have to take two steps; @@ -959,7 +959,7 @@ user@localhost:~/bats-file$ vagrant up The line above spins up a brand new virtualbox image and provisions with prerequisites. -However, as the tests require not to be on a network share due to running commands eg: `mknod`, the files are shared into the VM by `rsync` module. Rsync in vagrant only runs initialy and stops. During the active development, you regularly change files and might want to see the impact. To achieve that, you have to use auto rsync. +However, as the tests require not to be on a network share due to running commands eg: `mknod`, the files are shared into the VM by `rsync` module. Rsync in vagrant only runs initially and stops. During the active development, you regularly change files and might want to see the impact. To achieve that, you have to use auto rsync. > `auto-rsync` is a long running command. It means that it has to run on terminal screen as long as the VM is up and running. So, you have to keep this in a dedicated terminal screen.