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

Use bootstrap project in bootstrapping #9990

Merged
merged 1 commit into from
May 17, 2024
Merged

Use bootstrap project in bootstrapping #9990

merged 1 commit into from
May 17, 2024

Conversation

sheaf
Copy link
Collaborator

@sheaf sheaf commented May 8, 2024

We need to use the cabal.bootstrap.project file to generate the bootstrap plans, otherwise we try to include test components when bootstrapping, which is not useful (and significantly complicates bootstrapping).

I forgot to include this change in 88737ef, but I used this change to generate the plans.


Template B: This PR does not modify behaviour or interface

  • Patch conforms to the coding conventions.
  • This does not need to be backported to older release branches; it applies to 3.13 onwards only.

@sheaf sheaf added merge me Tell Mergify Bot to merge and removed attention: needs-review labels May 8, 2024
@mergify mergify bot added the merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days label May 10, 2024
@Mikolaj Mikolaj force-pushed the bootstrap-project-1 branch from d26a5e0 to b31f666 Compare May 10, 2024 16:33
@alt-romes
Copy link
Collaborator

@mergify rebase

Copy link
Contributor

mergify bot commented May 17, 2024

rebase

❌ Unable to rebase: user alt-romes is unknown.

Please make sure alt-romes has logged in Mergify dashboard.

@ulysses4ever
Copy link
Collaborator

@mergify rebase

Copy link
Contributor

mergify bot commented May 17, 2024

rebase

✅ Branch has been successfully rebased

@ulysses4ever ulysses4ever force-pushed the bootstrap-project-1 branch from b31f666 to 9046b6f Compare May 17, 2024 13:22
@ulysses4ever
Copy link
Collaborator

@alt-romes Mergify is picky about accounts that can call commands like that, unfortunately. For a mere Rebase a non-admin user is better off with the GitHub UI, I think: there's an Update button usually, and if you click a dropdown menu button, you can change it from "merge master into feature branch" to "rebase feature on top of master" (not literally, but that's the meaning).

We need to use the cabal.bootstrap.project file to generate the bootstrap plans, otherwise we try to include test components when bootstrapping, which is not useful (and significantly complicates bootstrapping).
@Mikolaj Mikolaj force-pushed the bootstrap-project-1 branch from 9046b6f to 3c84288 Compare May 17, 2024 16:02
@mergify mergify bot merged commit 3b4b3e1 into master May 17, 2024
50 checks passed
@mergify mergify bot deleted the bootstrap-project-1 branch May 17, 2024 18:40
geekosaur added a commit that referenced this pull request May 21, 2024
geekosaur added a commit that referenced this pull request May 21, 2024
mergify bot added a commit that referenced this pull request May 23, 2024
* 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 <philderbeast@gmail.com>
Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com>
Co-authored-by: Artem Pelenitsyn <a.pelenitsyn@gmail.com>
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.

5 participants