Fix docs spellcheck failure in the IBM Db2 provider - #72203
Merged
Conversation
The nightly docs build fails spellcheck on the Db2 hook because the module name in the get_conn docstring is unquoted prose, so the checker treats part of it as a misspelled word.
eladkal
approved these changes
Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The nightly
Build documentation (--spellcheck-only)job has been failing on the new IBM Db2 provider: sphinxcontrib-spelling flagsdbiin theDb2Hook.get_conndocstring, because the module name is written as unquoted prose. Quoting it as an RST literal excludes it from the spellcheck, as the build's own error message recommends.Failing job: https://github.com/apache/airflow/actions/runs/33166271901/job/98838898069
Verified locally with
breeze build-docs ibm.db2 --spellcheck-only—Finished spell-checking successfully.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5) following the guidelines