Skip to content

Fix memory leak when using mandatory flag in CQs (backport #3560) #3572

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

Merged
merged 2 commits into from
Oct 13, 2021

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Oct 13, 2021

This is an automatic backport of pull request #3560 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.io/

MsgNo is defined for both mandatory flags and confirms,
but only confirms need to be kept track of in this module.

(cherry picked from commit 7ffb154)
@michaelklishin michaelklishin merged commit 9994032 into v3.9.x Oct 13, 2021
@michaelklishin michaelklishin deleted the mergify/bp/v3.9.x/pr-3560 branch October 13, 2021 15:39
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.

2 participants