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

Fix for #12877 as per @azeemism #13066

Merged
merged 1 commit into from
Jan 16, 2018

Conversation

jagritijoshi
Copy link

@jagritijoshi jagritijoshi commented Jan 9, 2018

Description

Fixed Magento Database Backup Command Fails

Fixed Issues (if relevant)

  1. [2.2.1] Magento Database Backup Command Fails (Fix included) #12877 : Magento Database Backup Command Fails (Fix included)

Contribution checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)

@avoelkl avoelkl self-assigned this Jan 9, 2018
@avoelkl avoelkl added this to the January 2018 milestone Jan 9, 2018
@jagritijoshi
Copy link
Author

@avoelkl Can you please send me invitation to join the community? So that I can assign bug to myself.

@avoelkl
Copy link
Contributor

avoelkl commented Jan 9, 2018

Hi @jagritijoshi,
Only Magento Github Maintainers and the Magento Community Engineering team can assign themselves to Pull Requests.
I just checked and saw that you are already part of the Magento Community Engineering Slack Team so I think this is all I can do for now :)

@magento-team magento-team merged commit bc434c1 into magento:2.2-develop Jan 16, 2018
magento-team pushed a commit that referenced this pull request Jan 16, 2018
@magento-engcom-team magento-engcom-team added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Jan 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in 2.2.x The issue has been fixed in 2.2 release line Progress: accept Release Line: 2.2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants