Skip to content

mergify: add backport label (backport #25050)#25064

Closed
mergify[bot] wants to merge 1 commit into7.xfrom
mergify/bp/7.x/pr-25050
Closed

mergify: add backport label (backport #25050)#25064
mergify[bot] wants to merge 1 commit into7.xfrom
mergify/bp/7.x/pr-25050

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Apr 14, 2021

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

Cherry-pick of 164bb5e has failed:

On branch mergify/bp/7.x/pr-25050
Your branch is up to date with 'origin/7.x'.

You are currently cherry-picking commit 164bb5ed42.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   .mergify.yml

no changes added to commit (use "git add" and/or "git commit -a")

To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/


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/

(cherry picked from commit 164bb5e)

# Conflicts:
#	.mergify.yml
@mergify mergify Bot added backport conflicts There is a conflict in the backported pull request labels Apr 14, 2021
@mergify mergify Bot assigned v1v Apr 14, 2021
@botelastic botelastic Bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 14, 2021
@botelastic
Copy link
Copy Markdown

botelastic Bot commented Apr 14, 2021

This pull request doesn't have a Team:<team> label.

@v1v v1v closed this Apr 14, 2021
@mergify mergify Bot deleted the mergify/bp/7.x/pr-25050 branch April 14, 2021 08:17
@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: Pull request #25064 opened

  • Start Time: 2021-04-14T08:12:54.245+0000

  • Duration: 12 min 49 sec

  • Commit: bc56c13

Trends 🧪

Image of Build Times

❕ Flaky test report

No test was executed to be analysed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport conflicts There is a conflict in the backported pull request needs_team Indicates that the issue/PR needs a Team:* label

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants