Fix misspellings in Go comments, log messages and error strings
I maintainer di solito rispondono entro 2 giorni
@oree-xx ci sta già lavorando.
Dal 3/11/2026.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- Mezza giornata
- Idoneità per principianti
- 85/100
Direzione di ricerca
Inizia da un'area, ad esempio pkg/app/piped/driftdetector, e correggi solo i refusi nei commenti, nei log e nelle stringhe di errore elencati nell'issue. Lascia invariati gli identificatori e salta i due commenti nei file .proto, che richiedono make gen/code. Esegui make test/go sui moduli toccati e tieni presente che pkg/app/pipedv1/plugin è un modulo Go separato. Il lavoro è completato quando le grafie elencate sono corrette nella tua area e i suoi test passano.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
What happened:
A spell check over the Go sources, protobuf definitions and test fixtures finds about 110 misspellings in comments, log messages and error strings.
Full list (file:line: wrong ==> right)
cmd/controlplane/ops.go:174: runnning ==> running
pkg/jwt/jwt.go:30: singed ==> signed, singled, sang, sung
pkg/configv1/application.go:473: splited ==> split
pkg/configv1/application.go:474: splited ==> split
pkg/configv1/application_test.go:242: sepcified ==> specified
pkg/configv1/application_test.go:285: sepcified ==> specified
pkg/app/piped/deploysource/deploysource.go:170: unsupport ==> unsupported
pkg/app/piped/apistore/applicationstore/store.go:37: specifiec ==> specific
pkg/app/piped/trigger/deployment.go:38: cound ==> could, count, found
pkg/app/piped/planner/kubernetes/kubernetes.go:134: choise ==> choice, choose
pkg/app/piped/planner/kubernetes/kubernetes_test.go:103: mutilple ==> multiple
pkg/app/piped/logpersister/persister.go:72: concurent ==> concurrent
pkg/app/piped/controller/scheduler.go:448: temination ==> termination
pkg/app/piped/controller/scheduler.go:885: evnet ==> event
pkg/app/piped/platformprovider/kubernetes/kubernetes.go:36: mouting ==> moulting, mounting, mouthing, muting, pouting
pkg/app/piped/platformprovider/kubernetes/loader.go:166: unsupport ==> unsupported
pkg/app/piped/platformprovider/kubernetes/resourcekey.go:212: comparation ==> comparison
pkg/app/piped/platformprovider/kubernetes/resourcekey.go:212: namesapce ==> namespace
pkg/app/piped/platformprovider/kubernetes/resourcekey.go:235: comparation ==> comparison
pkg/app/piped/platformprovider/kubernetes/resourcekey.go:235: namesapce ==> namespace
pkg/app/piped/driftdetector/terraform/detector.go:188: unsupport ==> unsupported
pkg/app/piped/driftdetector/terraform/detector.go:220: configurated ==> configured
pkg/app/piped/driftdetector/ecs/detector.go:401: configurated ==> configured
pkg/app/piped/driftdetector/cloudrun/detector.go:246: unsupport ==> unsupported
pkg/app/piped/driftdetector/cloudrun/detector.go:278: configurated ==> configured
pkg/app/piped/driftdetector/lambda/detector.go:217: followings ==> following
pkg/app/piped/driftdetector/lambda/detector.go:294: unsupport ==> unsupported
pkg/app/piped/driftdetector/lambda/detector.go:326: configurated ==> configured
pkg/app/piped/driftdetector/kubernetes/detector.go:215: splited ==> split
pkg/app/piped/driftdetector/kubernetes/detector.go:216: splited ==> split
pkg/app/piped/driftdetector/kubernetes/detector.go:216: splited ==> split
pkg/app/piped/driftdetector/kubernetes/detector.go:260: unsupport ==> unsupported
pkg/app/piped/driftdetector/kubernetes/detector.go:292: configurated ==> configured
pkg/app/piped/driftdetector/kubernetes/detector.go:431: unsupport ==> unsupported
pkg/app/piped/sourceprocesser/sourceprocesser.go:65: Rebuid ==> Rebuild
pkg/app/piped/sourceprocesser/sourceprocesser_test.go:92: attachement ==> attachment
pkg/app/piped/executor/stopsignal.go:35: excutor ==> executor
pkg/app/piped/executor/scriptrun/scriptrun.go:98: Runnnig ==> Running
pkg/app/piped/executor/scriptrun/scriptrun.go:108: srcipt ==> script
pkg/app/piped/executor/customsync/customsync.go:100: Runnnig ==> Running
pkg/app/piped/executor/customsync/rollback.go:84: Runnnig ==> Running
pkg/app/piped/executor/kubernetes/kubernetes.go:617: Anotate ==> Annotate
pkg/app/piped/executor/kubernetes/kubernetes_test.go:221: temlate ==> template
pkg/app/piped/executor/kubernetes/primary.go:39: trigered ==> triggered
pkg/app/piped/executor/kubernetes/rollback.go:185: Runnnig ==> Running
pkg/app/piped/executor/kubernetes/rollback.go:220: srcipt ==> script
pkg/app/piped/executor/kubernetes/traffic.go:160: unsupport ==> unsupported
pkg/app/piped/executor/kubernetes/traffic_test.go:53: speficied ==> specified
pkg/app/piped/livestatestore/livestatestore.go:81: thats ==> that's
pkg/app/piped/livestatestore/livestatestore.go:83: thats ==> that's
pkg/app/piped/livestatestore/livestatestore.go:85: thats ==> that's
pkg/app/piped/livestatestore/livestatestore.go:87: thats ==> that's
pkg/app/piped/livestatestore/livestatestore.go:89: thats ==> that's
pkg/app/piped/livestatestore/kubernetes/reflector.go:168: Kubernets ==> Kubernetes
pkg/app/pipedv1/apistore/applicationstore/store.go:35: specifiec ==> specific
pkg/app/pipedv1/trigger/deployment.go:38: cound ==> could, count, found
pkg/app/pipedv1/plugin/terraform/config/config.go:58: workpsace ==> workspace
pkg/app/pipedv1/plugin/analysis/config/piped.go:126: unknow ==> unknown
pkg/app/pipedv1/plugin/kubernetes_multicluster/provider/kubernetes.go:37: mouting ==> moulting, mounting, mouthing, muting, pouting
pkg/app/pipedv1/plugin/kubernetes_multicluster/deployment/misc_test.go:94: temlate ==> template
pkg/app/pipedv1/plugin/kubernetes/provider/kubernetes.go:38: mouting ==> moulting, mounting, mouthing, muting, pouting
pkg/app/pipedv1/plugin/kubernetes/deployment/baseline_test.go:231: weired ==> weird
pkg/app/pipedv1/plugin/kubernetes/deployment/baseline_test.go:277: weired ==> weird
pkg/app/pipedv1/plugin/kubernetes/deployment/baseline_test.go:323: weired ==> weird
pkg/app/pipedv1/plugin/kubernetes/deployment/baseline_test.go:402: weired ==> weird
pkg/app/pipedv1/plugin/kubernetes/deployment/baseline_test.go:448: weired ==> weird
pkg/app/pipedv1/plugin/kubernetes/deployment/baseline_test.go:494: weired ==> weird
pkg/app/pipedv1/plugin/kubernetes/deployment/misc_test.go:96: temlate ==> template
pkg/app/pipedv1/plugin/kubernetes/deployment/pipeline.go:48: splitted ==> split
pkg/app/pipedv1/controller/scheduler.go:449: temination ==> termination
pkg/app/pipedv1/controller/scheduler.go:890: evnet ==> event
pkg/app/pipedv1/controller/stopsignal.go:35: excutor ==> executor
pkg/app/pipedv1/sourceprocesser/sourceprocesser.go:65: Rebuid ==> Rebuild
pkg/app/pipedv1/sourceprocesser/sourceprocesser_test.go:92: attachement ==> attachment
pkg/app/server/httpapi/auth_handler.go:65: imcoming ==> incoming
pkg/app/server/service/pipedservice/service.proto:142: releated ==> related
pkg/app/server/grpcapi/web_api.go:1296: porject ==> project
pkg/app/ops/handler/handler_test.go:182: mis ==> miss, mist
pkg/app/ops/mysqlensurer/sqlsensurer.go:22: funtions ==> functions
pkg/app/ops/deploymentchaincontroller/updater.go:133: missng ==> missing
pkg/config/application.go:773: splited ==> split
pkg/config/application.go:774: splited ==> split
pkg/config/application_terraform.go:36: workpsace ==> workspace
pkg/config/application_test.go:294: sepcified ==> specified
pkg/config/application_test.go:337: sepcified ==> specified
pkg/config/config.go:217: plaform ==> platform
pkg/config/piped.go:782: unknow ==> unknown
pkg/config/testdata/application/cloudrun-app-canary.yaml:23: thre ==> three, there, their, the
pkg/config/testdata/application/k8s-app-bluegreen-with-analysis.yaml:3: againts ==> against
pkg/config/testdata/application/k8s-app-canary.yaml:159: comparision ==> comparison
pkg/config/testdata/application/lambda-app-canary.yaml:18: thre ==> three, there, their, the
pkg/plugin/sdk/logpersister/persister.go:75: concurent ==> concurrent
pkg/plugin/sdk/diff/diff.go:238: unsupport ==> unsupported
pkg/plugin/sdk/diff/diff.go:245: seccond ==> second
pkg/diff/diff.go:112: calulates ==> calculates
pkg/diff/diff.go:303: unsupport ==> unsupported
pkg/diff/diff.go:310: seccond ==> second
pkg/model/application.proto:64: trigered ==> triggered
pkg/model/common_test.go:59: kuberntes ==> kubernetes
pkg/model/project.go:544: nott ==> not
pkg/model/project_test.go:510: doen't ==> doesn't
pkg/model/stage.go:53: splitted ==> split
pkg/model/stage.go:92: splitted ==> split
pkg/rpc/rpcauth/interceptor.go:205: unsufficient ==> insufficient
tool/codegen/protoc-gen-auth/main.go:100: pasing ==> parsing, passing, posing
tool/actions-plan-preview/main.go:122: conficts ==> conflicts, convicts
tool/actions-plan-preview/planpreview_test.go:599: chages ==> changes, charges
What you expected to happen:
Comments, log messages and error strings are spelled correctly.
How to fix:
- Fix text only: comments, log messages, error strings and test names. Do not rename identifiers (variables, functions, struct fields, JSON tags), since that changes behaviour or the public API.
- Two hits are in
.protocomments (pkg/model/application.proto,pkg/app/server/service/pipedservice/service.proto). Changing them requires runningmake gen/codeand committing the regenerated files, so it is fine to leave them for a separate PR. - Please split the work into a few small PRs, for example one per top-level area (
pkg/app/piped,pkg/app/pipedv1,pkg/config+pkg/configv1, everything else). Small PRs get reviewed faster. - Run
make test/goon the touched modules. Plugin modules underpkg/app/pipedv1/plugin/are separate Go modules, see the Testing section of CONTRIBUTING.md. - The list was produced with
codespell(https://github.com/codespell-project/codespell). Known false positives already removed:listIn,commitish,numer,upToDate,als,unparseable.
Environment:
- Checked against
masterat b2c679c6f (1 Nov 2026).
- Lingua principale
- Go
- Stelle
- 1.4k
- Fork
- 391
- Merge medio
- 4g 1h
- PR unite (30g)
- 58
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di pipe-cd/pipecd
-
Applications at the repository root are not triggered by new commitsForse già presa @Daksha1611 l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 2 giorni
-
pipedv1 kubernetes plugins ignore trafficRouting.istio.host in K8S_TRAFFIC_ROUTINGForse già presa @Dhirenderchoudhary l’ha presa oggi. Aperta
Difficoltà 2/5 Mezza giornata Idoneità per principianti 74/100
pipe-cd/pipecd#7626 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 2 giorni
-
pipectl transfer restore application drops backed-up labelsForse già presa @bhavishyajain545 l’ha presa 1 giorno fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
pipe-cd/pipecd#7622 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
I maintainer di solito rispondono entro 2 giorni
Tutte le issue di pipe-cd/pipecd
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
docker-compose: postgres healthcheck should probe TCP (pg_isready -h localhost)Forse già presa @zezo-mohamed22 l’ha presa oggi. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
OneBusAway/watchdog#305 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
self-care self-care:agent-discoverability
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
githubnext/gh-cao#20928 ·
I maintainer di solito rispondono entro 1 giorno
-
automation documentation
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 70/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
SocialGouv/iterion#3287 ·
I maintainer di solito rispondono entro 1 giorno