diff options
| author | Taras Madan <tarasmadan@google.com> | 2025-08-19 15:53:14 +0200 |
|---|---|---|
| committer | Taras Madan <tarasmadan@google.com> | 2025-08-19 14:17:01 +0000 |
| commit | 0773c4252b9eda702503351c75aca73526a13b6c (patch) | |
| tree | 3a9ea716de1a24261099d001a093f6291f3977c8 /docs/maintaining.md | |
| parent | 7247b5c7fccc4b0e6008504269cb3537fcbdf93a (diff) | |
docs: fix misspellings
Gemini CLI experiments side effect.
Diffstat (limited to 'docs/maintaining.md')
| -rw-r--r-- | docs/maintaining.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/maintaining.md b/docs/maintaining.md index 43fe0bf06..fcffc36d0 100644 --- a/docs/maintaining.md +++ b/docs/maintaining.md @@ -18,7 +18,7 @@ Pull requests (PR) have only 2 options: `cla/google` check needs to pass before merging. CI testing generally needs to pass before merging.\ -Exceptions may be infrastrcture flakes (especially in external services: `codecov`, `ci/fuzzit`); +Exceptions may be infrastructure flakes (especially in external services: `codecov`, `ci/fuzzit`); one-off timeouts/OOMs (but not if this PR itself makes them much more frequent). All static checking warnings and testing errors are considered hard errors. @@ -28,12 +28,12 @@ Adding tests for new code and bug fixes is generally encouraged. Ask contributor However, some code is easier to test, while some is harder. Some examples of cases where it's easier to add tests (should be added): abstract functionalities without external dependencies -(e.g. parsers, data transformations, calculations); code with established testing infrastrcture +(e.g. parsers, data transformations, calculations); code with established testing infrastructure (adding new tests is just adding one more of the same). Examples of cases where it's harder to add tests (may be not added, but still welcome if one wants to go above and beyond): -code with external dependancies that are not easy to fake out (qemu, kernel, image, etc); -code without established testing infrastrcture where adding one test would require building -the whole infrastrcture first. +code with external dependencies that are not easy to fake out (qemu, kernel, image, etc); +code without established testing infrastructure where adding one test would require building +the whole infrastructure first. ## Use your judgement |
