make formatting of build-depends consistent
#10714
Open
+175
−157
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`*.cabal` files in this project presently have a mix of formatting of `build-depends`. Make them all consistent with: https://cabal.readthedocs.io/en/3.4/cabal-package.html No changes to any dependencies.
ulysses4ever
approved these changes
Jan 5, 2025
There was a problem hiding this comment.
Seems fine to me. Maybe a candidate to .git-blame-ignore-revs?..
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
*.cabalfiles in this project presently have a mix of formatting ofbuild-depends.Make them all consistent with:
https://cabal.readthedocs.io/en/3.4/cabal-package.html
There are no changes to any dependencies.
Please read Github PR Conventions and then fill in one of these two templates.
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: