From 51784a15b2e58bea172cb4d262a228ce0ee94705 Mon Sep 17 00:00:00 2001 From: Simon Josefsson Date: Wed, 26 Nov 2025 09:09:56 +0100 Subject: [PATCH] Fix typo of 'allows to' into 'allow one to' Found by Debian QA lintian tool: X: bingo: spelling-error-in-binary "allows to" "allows one to" [usr/bin/bingo] Signed-off-by: Simon Josefsson --- README.md | 6 +++--- main.go | 2 +- pkg/runner/runner.go | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 68f4605..7943617 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ At the end `bingo`, has following features: * Works also for non-Go projects. It only requires the tools to be written in Go. * No need to install `bingo` in order to **use** pinned tools. This avoids the "chicken & egg" problem. You only need `go build`. * Easy upgrade, downgrade, addition, and removal of the needed binary's version, with no risk of dependency conflicts. - * NOTE: Tools are **often** not following semantic versioning, so `bingo` allows to pin by commit ID. + * NOTE: Tools are **often** not following semantic versioning, so `bingo` allow one to pin by commit ID. * Immutable binary names. This creates a reliable way for users and CIs to use expected version of the binaries, reinstalling on-demand only if needed. * Works with all buildable Go projects, including pre Go modules and complex projects with complex directives like `replace`, `retract` or `exclude` statements. (e.g Prometheus) * Optional, automatic integration with Makefiles. @@ -81,7 +81,7 @@ go build -mod=mod -modfile .bingo/.mod -o=$GOBIN/- For example `go build -mod=mod -modfile .bingo/faillint.mod -o=$GOBIN/faillint-v1.5.0` -`bingo` allows to easily maintain a separate, nested Go Module for each binary. By default, it will keep it `.bingo/.mod` This allows to correctly pin the binary without polluting the main go module or other's tool module. +`bingo` allow one to easily maintain a separate, nested Go Module for each binary. By default, it will keep it `.bingo/.mod` This allow one to correctly pin the binary without polluting the main go module or other's tool module. ### Using Installed Tools @@ -262,7 +262,7 @@ bingo: 'go get' like, simple CLI that allows automated versioning of Go package level binaries (e.g required as dev tools by your project!) built on top of Go Modules, allowing reproducible dev environments. -'bingo' allows to easily maintain a separate, nested Go Module for each binary. +'bingo' allow one to easily maintain a separate, nested Go Module for each binary. For detailed examples and documentation see: https://github.com/bwplotka/bingo diff --git a/main.go b/main.go index a9c9816..3574a0a 100644 --- a/main.go +++ b/main.go @@ -24,7 +24,7 @@ func NewBingoCommand(logger *log.Logger) *cobra.Command { Go package level binaries (e.g required as dev tools by your project!) built on top of Go Modules, allowing reproducible dev environments. -'bingo' allows to easily maintain a separate, nested Go Module for each binary. +'bingo' allow one to easily maintain a separate, nested Go Module for each binary. For detailed examples and documentation see: https://github.com/bwplotka/bingo `, diff --git a/pkg/runner/runner.go b/pkg/runner/runner.go index 803f35c..1d80f84 100644 --- a/pkg/runner/runner.go +++ b/pkg/runner/runner.go @@ -21,7 +21,7 @@ import ( "github.com/efficientgo/core/errors" ) -// Runner allows to run certain commands against module aware Go CLI. +// Runner allow one to run certain commands against module aware Go CLI. type Runner struct { goCmd string insecure bool