Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃尡 grammar: removed doubles of the word "the" #2006

Merged
merged 1 commit into from Sep 27, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion TMP-LOGGING.md
Expand Up @@ -51,7 +51,7 @@ You can configure the logging implementation using
`"sigs.k8s.io/controller-runtime/pkg/log".SetLogger`. That
package also contains the convenience functions for setting up Zap.

You can get a handle to the the "root" logger using
You can get a handle to the "root" logger using
`"sigs.k8s.io/controller-runtime/pkg/log".Log`, and can then call
`WithName` to create individual named loggers. You can call `WithName`
repeatedly to chain names together:
Expand Down
4 changes: 2 additions & 2 deletions pkg/builder/options.go
Expand Up @@ -101,9 +101,9 @@ func (p projectAs) ApplyToWatches(opts *WatchesInput) {

var (
// OnlyMetadata tells the controller to *only* cache metadata, and to watch
// the the API server in metadata-only form. This is useful when watching
// the API server in metadata-only form. This is useful when watching
// lots of objects, really big objects, or objects for which you only know
// the the GVK, but not the structure. You'll need to pass
// the GVK, but not the structure. You'll need to pass
// metav1.PartialObjectMetadata to the client when fetching objects in your
// reconciler, otherwise you'll end up with a duplicate structured or
// unstructured cache.
Expand Down
2 changes: 1 addition & 1 deletion pkg/log/zap/zap.go
Expand Up @@ -101,7 +101,7 @@ func newConsoleEncoder(opts ...EncoderConfigOption) zapcore.Encoder {
return zapcore.NewConsoleEncoder(encoderConfig)
}

// Level sets Options.Level, which configures the the minimum enabled logging level e.g Debug, Info.
// Level sets Options.Level, which configures the minimum enabled logging level e.g Debug, Info.
// A zap log level should be multiplied by -1 to get the logr verbosity.
// For example, to get logr verbosity of 3, pass zapcore.Level(-3) to this Opts.
// See https://pkg.go.dev/github.com/go-logr/zapr for how zap level relates to logr verbosity.
Expand Down
2 changes: 1 addition & 1 deletion tools/setup-envtest/README.md
Expand Up @@ -91,7 +91,7 @@ Then, you have a few options for managing your binaries:
`--use-env` makes the command unconditionally use the value of
KUBEBUILDER_ASSETS as long as it contains the required binaries, and
`-i` indicates that we only ever want to work with installed binaries
(no reaching out the the remote GCS storage).
(no reaching out the remote GCS storage).

As noted about, you can use `ENVTEST_INSTALLED_ONLY=true` to switch `-i`
on by default, and you can use `ENVTEST_USE_ENV=true` to switch
Expand Down
2 changes: 1 addition & 1 deletion tools/setup-envtest/main.go
Expand Up @@ -192,7 +192,7 @@ Versions:
Z may also be '*' or 'x' to match a wildcard.
You may also just write X.Y, which means X.Y.*.

A version may be prefixed with '~' to match the the most recent Z release
A version may be prefixed with '~' to match the most recent Z release
in the given Y release ( [X.Y.Z, X.Y+1.0) ).

Finally, you may suffix the version with '!' to force checking the
Expand Down
2 changes: 1 addition & 1 deletion tools/setup-envtest/workflows/workflows.go
Expand Up @@ -25,7 +25,7 @@ func (f Use) Do(env *envp.Env) {
ctx := logr.NewContext(context.TODO(), env.Log.WithName("use"))
env.EnsureBaseDirs(ctx)
if f.UseEnv {
// the the env var unconditionally
// the env var unconditionally
if env.PathMatches(f.AssetsPath) {
env.PrintInfo(f.PrintFormat)
return
Expand Down