Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove accidentally introduced Cabal-hooks.cabal #10444

Merged
merged 1 commit into from
Oct 12, 2024
Merged

Conversation

geekosaur
Copy link
Collaborator

introduced accidentally while fixing conflicts in 5b4d226

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

Note that this is on the 3.12 LTS branch, not master. The *.cabal file is useless there because none of the code exists (correctly, since it requires 3.13+).

Copy link
Member

@Mikolaj Mikolaj left a comment

Choose a reason for hiding this comment

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

:D

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.

it happens...

@geekosaur geekosaur added merge me Tell Mergify Bot to merge and removed attention: needs-review labels Oct 11, 2024
@geekosaur
Copy link
Collaborator Author

Blocked on #10445, GHA moved ubuntu-latest to 24.04 which doesn't have ncurses5 so older ghcs won't run

introduced accidentally while fixing conflicts in 5b4d226
@mergify mergify bot merged commit 12d5db6 into 3.12 Oct 12, 2024
58 checks passed
@mergify mergify bot deleted the cleanup-hooks-3.12 branch October 12, 2024 00:15
@mergify mergify bot added the merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days label Oct 14, 2024
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 merge me Tell Mergify Bot to merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants