Skip to content

Conversation

@Kleidukos
Copy link
Member

Following #11231, this PR adds a README.md file in the files generated by cabal init.

@Kleidukos Kleidukos marked this pull request as draft October 18, 2025 19:01
@Kleidukos Kleidukos force-pushed the 11231-add-readme-to-cabal-init-project branch 2 times, most recently from ca0a2a4 to 226e685 Compare October 18, 2025 19:33
@Kleidukos Kleidukos force-pushed the 11231-add-readme-to-cabal-init-project branch 2 times, most recently from f3d1abe to e55841d Compare January 15, 2026 15:58
@Kleidukos Kleidukos marked this pull request as ready for review January 15, 2026 15:59
@Kleidukos Kleidukos force-pushed the 11231-add-readme-to-cabal-init-project branch from e55841d to 8dfc4fc Compare January 15, 2026 18:35
@Kleidukos Kleidukos force-pushed the 11231-add-readme-to-cabal-init-project branch from 8dfc4fc to 99254fc Compare January 15, 2026 19:21
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.

Cool 😎

@Kleidukos Kleidukos added squash+merge me Tell Mergify Bot to squash-merge and removed attention: needs-review labels Jan 19, 2026
@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 Jan 19, 2026
@mergify
Copy link
Contributor

mergify bot commented Jan 21, 2026

Merge Queue Status

✅ The pull request has been merged at 99254fc

This pull request spent 2 hours 4 minutes 52 seconds in the queue, including 1 hour 54 minutes 39 seconds running CI.
The checks were run on draft #11449.

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 bot added a commit that referenced this pull request Jan 21, 2026
@mergify mergify bot merged commit c427548 into haskell:master Jan 21, 2026
236 of 244 checks passed
@mergify mergify bot removed the queued label Jan 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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

Development

Successfully merging this pull request may close these issues.

3 participants