-
Notifications
You must be signed in to change notification settings - Fork 698
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
Rename projects to have .project
extension
#9958
Conversation
This looks good to me! A minor point and this is liable to endless bikeshedding so feel free to ignore, but I have a mild preference for |
@TeofilC thanks for the good suggestion but for this pull request I don't want depart too much from what we have by scattering the projects. With
|
Unrelated to this pull request but your suggested change @TeofilC prompted me to review the names I used with Updo. There are currently two sets;
|
Label merge+no rebase is necessary when the pull request is from an organisation. |
- Rename cabal.bootstrap.project - Rename cabal.meta.project - Rename cabal.validate-libonly.project - Rename cabal.validate.project - Rename cabal.release.project
0c195fc
to
d8147f6
Compare
CI-related backport |
@mergify backport 3.12 |
✅ Backports have been created
|
* Rename projects to cabal.*.project - Rename cabal.bootstrap.project - Rename cabal.meta.project - Rename cabal.validate-libonly.project - Rename cabal.validate.project - Rename cabal.release.project (cherry picked from commit d8147f6) # Conflicts: # .github/workflows/quick-jobs.yml # Makefile # cabal.bootstrap.project * Fix conflict with #9990 --------- Co-authored-by: Phil de Joux <[email protected]> Co-authored-by: brandon s allbery kf8nh <[email protected]> Co-authored-by: Artem Pelenitsyn <[email protected]>
Fixes #9925, renaming project files to have a
.project
extension.Template Β: This PR does not modify
cabal
behaviour (documentation, tests, refactoring, etc.)Include the following checklist in your PR: