Skip to content

Conversation

HeladoDeBrownie
Copy link
Contributor

It appears to be either a typo or a leftover. It's the only instance of the word in the docs and is very close to a word that appears several times.

i don't believe this needs a separate issue because it looks like a simple typo fix to me

  • 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).

It appears to be either a typo or a leftover. It's the only instance of
the word in the docs and is very close to a word that appears several
times.
Copy link
Collaborator

@ulysses4ever ulysses4ever left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@geekosaur
Copy link
Collaborator

You can add the merge me label when you're ready.

@HeladoDeBrownie
Copy link
Contributor Author

it's ready to merge, go ahead

@geekosaur geekosaur added the merge me Tell Mergify Bot to merge label Sep 3, 2025
@mergify mergify bot added ready and waiting Mergify is waiting out the cooldown period merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days labels Sep 3, 2025
mergify bot added a commit that referenced this pull request Sep 5, 2025
@mergify mergify bot merged commit 6915c20 into haskell:master Sep 5, 2025
249 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge ready and waiting Mergify is waiting out the cooldown period
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants