Skip to content

Commit b2ef9d0

Browse files
deiningbep
authored andcommitted
Bump GitHub workflow actions to their latest versions
1 parent 64fc57c commit b2ef9d0

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

.github/workflows/test.yml

+2-2
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ jobs:
1212
runs-on: ${{ matrix.platform }}
1313
steps:
1414
- name: Install Go
15-
uses: actions/setup-go@v3
15+
uses: actions/setup-go@v4
1616
with:
1717
go-version: ${{ matrix.go-version }}
1818
- name: Install staticcheck
@@ -25,7 +25,7 @@ jobs:
2525
run: echo "$(go env GOPATH)/bin" >> $GITHUB_PATH
2626
shell: bash
2727
- name: Checkout code
28-
uses: actions/checkout@v1
28+
uses: actions/checkout@v3
2929
- name: Fmt
3030
if: matrix.platform != 'windows-latest' # :(
3131
run: "diff <(gofmt -d .) <(printf '')"

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -68,9 +68,9 @@ func main() {
6868

6969
## Differences to Cobra
7070

71-
You have access to the `*cobra.Command` pointer so there's not much you cannot do with this project compared to the more low-level Cobra, but there's one small, but imortant difference:
71+
You have access to the `*cobra.Command` pointer so there's not much you cannot do with this project compared to the more low-level Cobra, but there's one small, but important difference:
7272

73-
Cobra only treats the first level of misspelled commands as an `unknown command` with "Did you mean this?" suggestions, see [see this issue](https://github.com/spf13/cobra/pull/1500) for more context. The reason this is, is because of the ambiguity between sub command names and command arguments, but that is throwing away a very useful feature for a not very good reason. We recently rewrote [Hugo's CLI](https://github.com/gohugoio/hugo) using this poackage, and found only one sub command that needed to be adjusted to avoid this ambiguity.
73+
Cobra only treats the first level of misspelled commands as an `unknown command` with "Did you mean this?" suggestions, see [see this issue](https://github.com/spf13/cobra/pull/1500) for more context. The reason for this is the ambiguity between sub-command names and command arguments, but that is throwing away a very useful feature for a not very good reason. We recently rewrote [Hugo's CLI](https://github.com/gohugoio/hugo) using this package, and found only one sub command that needed to be adjusted to avoid this ambiguity.
7474

7575

7676

0 commit comments

Comments
 (0)