chore: fix typos in native service comments and strings - #206
Conversation
Fix spelling mistakes in comments, log messages, and doc strings across compute-plane, control-plane, and invocation-plane services, plus their shared Go libraries and the container-cache Helm chart. Comment and string content only, no identifiers or public field names were renamed. NO-REF Signed-off-by: mesutoezdil <mesudozdil@gmail.com>
|
🎉 This PR is included in version nvcf-function-autoscaler-v1.18.5 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version nvcf-container-cache-v0.27.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version nvcf-worker-task-v1.0.7 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version nvcf-invocation-service-v0.8.8 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version nvcf-helm-reval-api-v0.4.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version nvcf-ess-agent-v1.4.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
3 participants
TL;DR
Fixed spelling mistakes in comments, log/error messages, and doc strings across nvca, nvsnap, worker-task, ess-agent, byoo-otel-collector, helm-reval, function-autoscaler, http-invocation, the shared Go libraries, and the container-cache Helm chart. Comment and string content only, no identifier, field, or flag was renamed.
For the Reviewer
Verified with gofmt, py_compile, bash -n, and codespell that nothing else regressed. Deliberately left out a few codespell hits that turned out to be real identifiers already used consistently across the codebase (overrideable, unprobableReason, allReady) since fixing only the prose next to them would make things worse, not better. Also left out the vendored consul-template/vault SDK source under ess-agent, Kubernetes-generated files, and the vendored OpenAI OpenAPI spec in vanity-gateway.
Issues
NO-REF