This is an automated email from the ASF dual-hosted git repository.
sbp pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tooling-trusted-releases.git
The following commit(s) were added to refs/heads/main by this push:
new f5c9432 Fix typos
f5c9432 is described below
commit f5c94324b0d502bf0b90f5aec66d48dfa3da554c
Author: John Bampton <[email protected]>
AuthorDate: Wed Nov 5 20:50:44 2025 +1000
Fix typos
General spelling clean up
---
atr/api/__init__.py | 2 +-
atr/docs/code-conventions.html | 4 ++--
atr/docs/code-conventions.md | 2 +-
atr/templates/committee-view.html | 2 +-
scripts/interface_privacy.py | 2 +-
5 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/atr/api/__init__.py b/atr/api/__init__.py
index ac6419e..bcbb087 100644
--- a/atr/api/__init__.py
+++ b/atr/api/__init__.py
@@ -730,7 +730,7 @@ async def release_announce(data:
models.api.ReleaseAnnounceArgs) -> DictResponse
After a vote on a release has passed, if everything is in order and all
paths are correct, the release can be announced. This will send an email to
- the specified announement address, and promote the release to the finished
+ the specified announcement address, and promote the release to the finished
release phase. Once announced, a release is final and cannot be changed.
"""
asf_uid = _jwt_asf_uid()
diff --git a/atr/docs/code-conventions.html b/atr/docs/code-conventions.html
index 4487cbe..c9ff852 100644
--- a/atr/docs/code-conventions.html
+++ b/atr/docs/code-conventions.html
@@ -205,7 +205,7 @@ a or b and c == d or not e or f
# Prefer
(a or b) and (c == d) or (not e) or f
</code></pre>
-<p>Because <code>f</code> is not a complex expression, it does not get
parenthesised. Also because this rule is about subexpressions only, we do not
put parethenses around the top level.</p>
+<p>Because <code>f</code> is not a complex expression, it does not get
parenthesised. Also because this rule is about subexpressions only, we do not
put parentheses around the top level.</p>
<pre><code class="language-python"># Avoid
if (a or b):
...
@@ -218,7 +218,7 @@ if a or b:
<p>Place comments on dedicated lines preceding the relevant code block.
Comments at the ends of lines are strictly reserved for linter or type checker
directives. This convention enhances code scannability for such directives.
General comments must not appear at the end of code lines. Keep comments
concise, using sentence case without terminal punctuation. Each sentence
forming a comment must occupy its own line.</p>
<code></code><h3 id="prefer-explicit-checks-over-assert">Prefer explicit
checks over assert</h3>
<p>We do not use <code>assert</code>. If you need to guard against invalid
states or inputs, use standard <code>if</code> checks and raise appropriate
exceptions. If you need to help type checkers understand the type of a variable
within a specific code block, in other words if you need to narrow a type, then
use <code>if isinstance(...)</code> or <code>if not isinstance(...)</code> as
appropriate.</p>
-<code></code><h3
id="never-use-case-when-pattern-matching-exhausive-types">Never use case _ when
pattern matching exhausive types</h3>
+<code></code><h3
id="never-use-case-when-pattern-matching-exhaustive-types">Never use case _
when pattern matching exhaustive types</h3>
<p>Using <code>case _</code> breaks type checking in such situations.</p>
<h2 id="html">HTML</h2>
<h3 id="use-sentence-case-for-headings-form-labels-and-submission-buttons">Use
sentence case for headings, form labels, and submission buttons</h3>
diff --git a/atr/docs/code-conventions.md b/atr/docs/code-conventions.md
index 6742be2..4408c95 100644
--- a/atr/docs/code-conventions.md
+++ b/atr/docs/code-conventions.md
@@ -332,7 +332,7 @@ Place comments on dedicated lines preceding the relevant
code block. Comments at
We do not use `assert`. If you need to guard against invalid states or inputs,
use standard `if` checks and raise appropriate exceptions. If you need to help
type checkers understand the type of a variable within a specific code block,
in other words if you need to narrow a type, then use `if isinstance(...)` or
`if not isinstance(...)` as appropriate.
-### Never use `case _` when pattern matching exhausive types
+### Never use `case _` when pattern matching exhaustive types
Using `case _` breaks type checking in such situations.
diff --git a/atr/templates/committee-view.html
b/atr/templates/committee-view.html
index c651777..f3a0d7f 100644
--- a/atr/templates/committee-view.html
+++ b/atr/templates/committee-view.html
@@ -40,7 +40,7 @@
</div>
</div>
- {# Allow tooling to assocaite keys for testing #}
+ {# Allow tooling to associate keys for testing #}
{% if (not is_standing) or (committee.name == "tooling") %}
<div class="card mb-4">
<div class="card-header bg-light">
diff --git a/scripts/interface_privacy.py b/scripts/interface_privacy.py
index 54c970f..783c498 100755
--- a/scripts/interface_privacy.py
+++ b/scripts/interface_privacy.py
@@ -17,7 +17,7 @@
# under the License.
# TODO: We want to go the other way around too
-# In other words, finding underscoreless functions which are not accesssed
externally
+# In other words, finding underscoreless functions which are not accessed
externally
import ast
import enum
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
