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

merge-queue: embarking main (f012bfa) and #426 together #428

Closed
wants to merge 6 commits into from

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Jul 14, 2022

🎉 This combination of pull requests has been checked successfully 🎉

Branch main (f012bfa) and #426 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #426.
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="build-frontend"
  • check-success="buildkite/primer-app/pr/required-nix-ci"
  • check-success="deploy-to-chromatic"

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

georgefst and others added 6 commits July 14, 2022 12:04
This is a placeholder, pending a discussion around how to display and log errors.
NB this is an internal error condition which should never actually occur.
This replaces the previous hardcoded trees.

Note that we don't yet display a definition's name or type. These will be added in due course, once we've made some design decisions about how to lay out multiple trees.

We also currently require that the session contains precisely one editable module, throwing errors otherwise. We will some day relax this decision, once UX issues have been worked out.
With the previous style, further indentation was needed for each new check. Instead, we now utilise early returns to keep a flatter tree.
@mergify
Copy link
Author

mergify bot commented Jul 14, 2022

The pull request #426 is mergeable

@mergify mergify bot closed this Jul 14, 2022
@mergify mergify bot deleted the mergify/merge-queue/main/426 branch July 14, 2022 14:57
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