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

snapshots: serialize version file first (backport #27192) #27203

Merged
merged 1 commit into from
Aug 18, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Aug 17, 2022

This is an automatic backport of pull request #27192 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

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

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

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

serialize version file first

(cherry picked from commit c1111fa)
@mergify mergify bot added the automerge Merge this Pull Request automatically once CI passes label Aug 17, 2022
@willhickey willhickey removed the automerge Merge this Pull Request automatically once CI passes label Aug 17, 2022
@mergify mergify bot added the automerge Merge this Pull Request automatically once CI passes label Aug 17, 2022
@willhickey
Copy link
Contributor

willhickey commented Aug 17, 2022

Is it OK to wait until after 11.7 is tagged to merge this PR?

Discussion of the plan here (and in the parent message I'm replying to):
https://discord.com/channels/428295358100013066/910937142182682656/1009501986099572806

Not sure when 11.7 will be tagged but I'm aiming for this evening or tomorrow.

@willhickey willhickey added the no-automerge Prevent the automerge label from being applied label Aug 17, 2022
@apfitzge apfitzge removed the automerge Merge this Pull Request automatically once CI passes label Aug 17, 2022
@willhickey willhickey added automerge Merge this Pull Request automatically once CI passes and removed no-automerge Prevent the automerge label from being applied labels Aug 18, 2022
@mergify mergify bot removed the automerge Merge this Pull Request automatically once CI passes label Aug 18, 2022
@mergify
Copy link
Contributor Author

mergify bot commented Aug 18, 2022

automerge label removed due to a CI failure

@mergify mergify bot added automerge Merge this Pull Request automatically once CI passes and removed automerge Merge this Pull Request automatically once CI passes labels Aug 18, 2022
@mergify
Copy link
Contributor Author

mergify bot commented Aug 18, 2022

automerge label removed due to a CI failure

@mergify mergify bot added the automerge Merge this Pull Request automatically once CI passes label Aug 18, 2022
@mergify
Copy link
Contributor Author

mergify bot commented Aug 18, 2022

automerge label removed due to a CI failure

@mergify mergify bot added automerge Merge this Pull Request automatically once CI passes and removed automerge Merge this Pull Request automatically once CI passes labels Aug 18, 2022
@mergify mergify bot merged commit 8a30642 into v1.11 Aug 18, 2022
@mergify mergify bot deleted the mergify/bp/v1.11/pr-27192 branch August 18, 2022 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge this Pull Request automatically once CI passes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants