Ignore haddocks directory

[philderbeast]

Fixes #11638.

I also found and fixed a typo that typos missed, here I split a/b so that the typo is detected in b:

$ git diff
diff --git a/fix-whitespace.yaml b/fix-whitespace.yaml
index 7ab454137..a2b3f54f6 100644
--- a/fix-whitespace.yaml
+++ b/fix-whitespace.yaml
@@ -19,7 +19,7 @@
 # 3) included-files is a white-list of files,
 # 4) excluded-files is a black-list of included-files.
 #
-# The extended glob pattern can be used to specify file/direcotory names.
+# The extended glob pattern can be used to specify file and direcotory names.
 # For details, see http://hackage.haskell.org/package/filemanip-0.3.6.3/docs/System-FilePath-GlobPattern.html
 #
 included-dirs:

$ typos fix-whitespace.yaml
error: `direcotory` should be `directory`
   ╭▸ fix-whitespace.yaml:22:61
   │
22 │ # The extended glob pattern can be used to specify file and direcotory names.
   ╰╴                                                            ━━━━━━━━━━

I get the same typo detection if I run make hs-typos.

---

• Patches conform to the coding conventions.
• Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-03-21 18:52 UTC · Rule: default
• ✅ Checks started · on draft merge queue: embarking master (8730d5b) and #11639 together #11642
• 🚫 Left the queue — 2026-03-21 19:06 UTC · at 6e08afb892b9464eeebd5a167b93b57009c96ebd

This pull request spent 14 minutes 31 seconds in the queue, including 3 minutes 45 seconds running CI.

Required conditions to merge

• any of [🛡 GitHub branch protection]:
  • check-neutral = Doctest Cabal
  • check-skipped = Doctest Cabal
  • check-success = Doctest Cabal
• any of [🛡 GitHub branch protection]:
  • check-neutral = Meta checks
  • check-skipped = Meta checks
  • check-success = Meta checks
• any of [🛡 GitHub branch protection]:
  • check-neutral = Validate post job
  • check-skipped = Validate post job
  • check-success = Validate post job
• any of [🛡 GitHub branch protection]:
  • check-neutral = Bootstrap post job
  • check-skipped = Bootstrap post job
  • check-success = Bootstrap post job
• #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • Ignore haddocks directory #11639
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • Ignore haddocks directory #11639
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Ignore haddocks directory #11639
• any of [🛡 GitHub branch protection]:
  • check-success = docs/readthedocs.org:cabal
  • check-neutral = docs/readthedocs.org:cabal
  • check-skipped = docs/readthedocs.org:cabal
• any of [🛡 GitHub branch protection]:
  • check-success = fourmolu
  • check-neutral = fourmolu
  • check-skipped = fourmolu
• any of [🛡 GitHub branch protection]:
  • check-success = hlint
  • check-neutral = hlint
  • check-skipped = hlint
• any of [🛡 GitHub branch protection]:
  • check-success = whitespace
  • check-neutral = whitespace
  • check-skipped = whitespace
• any of [🛡 GitHub branch protection]:
  • check-success = Check sdist post job
  • check-neutral = Check sdist post job
  • check-skipped = Check sdist post job
• any of [🛡 GitHub branch protection]:
  • check-success = Changelogs
  • check-neutral = Changelogs
  • check-skipped = Changelogs

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

• ❌ Doctest Cabal

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[geekosaur]

@Mergifyio rebase

[mergify]

rebase

❌ Pull request can't be updated with latest base branch changes

Details

Mergify needs the author permission to update the base branch of the pull request.
@philderbeast needs to authorize modification on its head branch.