Skip to content

merge-queue: embarking main (5f8b303) and #379 together#409

Closed
mergify[bot] wants to merge 3 commits intomainfrom
mergify/merge-queue/main/379
Closed

merge-queue: embarking main (5f8b303) and #379 together#409
mergify[bot] wants to merge 3 commits intomainfrom
mergify/merge-queue/main/379

Conversation

@mergify
Copy link
Copy Markdown

@mergify mergify Bot commented Apr 25, 2022

🎉 This combination of pull requests has been checked successfully 🎉

Branch main (5f8b303) and #379 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #379.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

  • base=main
  • check-success="buildkite/primer/pr/required"

More informations about Mergify merge queue can be found in the documentation.

Mergify commands

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the queue rules

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

brprice and others added 3 commits April 25, 2022 17:14
This makes renaming modules a lot slicker, as we can do more
generically.
The reason for the slightly convoluted implementation is that I am
looking forward to when we have multiple editable modules, where we need
to edit multiple modules (as they all may contain references to the
renamed module). A potential optimisation is only checking for name
clashes with imports and not rewriting theose modules, since we do not
support renaming imports, and imports cannot depend on the editable
module.

I also take the chance to simplify the test code which does module
renaming, now that the idea has been properly implemented in the
library, with name clash detection. It is not worth making the library
more complex or exposing an "unsafe" version for one use in testsuite
(which intentionally clashes names, in order to merge modules).
@mergify
Copy link
Copy Markdown
Author

mergify Bot commented Apr 25, 2022

The pull request #379 is mergeable

@mergify mergify Bot closed this Apr 25, 2022
@mergify mergify Bot deleted the mergify/merge-queue/main/379 branch April 25, 2022 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant