Skip to content

doc: add UV setup details to README.md#11823

Merged
mergify[bot] merged 2 commits into
haskell:masterfrom
artem-hermes-bot:hermes-artem/uv-setup-docs
May 24, 2026
Merged

doc: add UV setup details to README.md#11823
mergify[bot] merged 2 commits into
haskell:masterfrom
artem-hermes-bot:hermes-artem/uv-setup-docs

Conversation

@ulysses4ever
Copy link
Copy Markdown
Collaborator

@ulysses4ever ulysses4ever commented May 14, 2026

This is towards #11818 @philderbeast @geekosaur Since there was no specification for what the new piece of documentation should achieve, I unleashed my AI bot on it. The result looks legit but maybe you guys had something different in mind?

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

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

@ulysses4ever ulysses4ever force-pushed the hermes-artem/uv-setup-docs branch from f5bbd02 to b00904a Compare May 14, 2026 00:10
@Bodigrim Bodigrim mentioned this pull request May 16, 2026
Closed
@philderbeast philderbeast mentioned this pull request May 20, 2026
Open
zlonast
zlonast reviewed May 22, 2026
View reviewed changes
Comment thread doc/README.md Outdated
@ulysses4ever ulysses4ever added the squash+merge me Tell Mergify Bot to squash-merge label May 22, 2026
@ulysses4ever
Copy link
Copy Markdown
Collaborator Author

ulysses4ever commented May 22, 2026 •
edited
Loading

@hasufell can you help with the release pipeline: I don't understand why it runs on PRs like this one --- I thought you said it needs a special label? Also, why it fails here... (see GitHub Actions pane above or here's a direct link to one of the many failing jobs: https://github.com/haskell/cabal/actions/runs/26291120700/job/77391368065?pr=11823)

@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 queued labels May 22, 2026
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 24, 2026 •
edited
Loading

Merge Queue Status

This pull request spent 1 hour 56 minutes 4 seconds in the queue, including 1 hour 23 minutes 57 seconds running CI.

Waiting for any of
  • check-neutral = Validate post job
  • check-skipped = Validate post job
  • check-success = Validate post job
All conditions
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • 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 = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • 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:

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.

mergify Bot added a commit that referenced this pull request May 24, 2026
@mergify
Merge of #11823
42a3ce8
@mergify mergify Bot mentioned this pull request May 24, 2026
Closed
86 tasks
mergify Bot added a commit that referenced this pull request May 24, 2026
@mergify
Merge of #11823
6752775
@mergify mergify Bot mentioned this pull request May 24, 2026
Closed
86 tasks
@mergify mergify Bot added dequeued and removed queued labels May 24, 2026
@zlonast
Copy link
Copy Markdown
Collaborator

zlonast commented May 24, 2026

@mergify rebase

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 24, 2026

rebase

❌ Unable to rebase: Mergify can't impersonate zlonast

Details

User zlonast used as bot_account is unknown. Please make sure {login} exists and has logged into the Mergify dashboard.

@zlonast
Copy link
Copy Markdown
Collaborator

zlonast commented May 24, 2026

@mergify update

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 24, 2026

update

❌ 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.
@ulysses4ever needs to authorize modification on its head branch.

@ulysses4ever
Copy link
Copy Markdown
Collaborator Author

ulysses4ever commented May 24, 2026

@mergify update

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 24, 2026

update

❌ 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.
@ulysses4ever needs to authorize modification on its head branch.

@ulysses4ever
Copy link
Copy Markdown
Collaborator Author

ulysses4ever commented May 24, 2026

@mergify rebase

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 24, 2026

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.
@ulysses4ever needs to authorize modification on its head branch.

@ulysses4ever ulysses4ever force-pushed the hermes-artem/uv-setup-docs branch from b01fa80 to ec0ce56 Compare May 24, 2026 20:26
@ulysses4ever
Copy link
Copy Markdown
Collaborator Author

ulysses4ever commented May 24, 2026

GitHub UI did the trick

@mergify mergify Bot added queued and removed dequeued labels May 24, 2026
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 24, 2026 •
edited
Loading

Merge Queue Status

  • ✅ Entered queue — 2026-05-24 22:08 UTC · Rule: squash-merge
  • ✅ Checks skipped · PR is already up-to-date
  • ✅ Merged — 2026-05-24 22:19 UTC · at ec0ce560ed0f66360194435e689dec1c0a586692 · squash

This pull request spent 11 minutes 20 seconds in the queue, including 3 seconds running CI.

Required conditions to merge
  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • 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 = Validate post job
    • check-neutral = Validate post job
    • check-skipped = Validate post job
  • 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 = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • 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

@mergify mergify Bot merged commit 802596a into haskell:master May 24, 2026
63 checks passed
@mergify mergify Bot removed the queued label May 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@zlonast zlonast zlonast approved these changes

@ffaf1 ffaf1 ffaf1 approved these changes

Assignees

No one assigned

Labels

merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days ready and waiting Mergify is waiting out the cooldown period squash+merge me Tell Mergify Bot to squash-merge

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@ulysses4ever @zlonast @ffaf1