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

Fixed 19371-Attribute Heading border misaligned. #19373

Closed

Conversation

suryakant-krish
Copy link
Contributor

Description (*)

Attribute Heading border misaligned.

Fixed Issues (if relevant)

  1. Attribute Heading border misaligned. #19371: Attribute Heading border misaligned.

Manual testing scenarios (*)

  1. Login to admin panel > Stores > Attribute sets > choose any attribute.
  2. Edit Attribute set name heading border.

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)

@magento-engcom-team
Copy link
Contributor

Hi @suryakant-krish. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento-engcom-team give me test instance - deploy test instance based on PR changes
  • @magento-engcom-team give me 2.2-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

@orlangur
Copy link
Contributor

@suryakant-krish please squash changes into a single commit. Also, note, that nowadays any changes must be delivered to 2.3-develop first.

@sivaschenko
Copy link
Member

@suryakant-krish please port this pull request to 2.3-develop branch.

@sidolov
Copy link
Contributor

sidolov commented Feb 6, 2019

Hi @suryakant-krish , please, resolve merge conflicts

@suryakant-krish
Copy link
Contributor Author

@sidolov,

I have resolved conflicts. please review that.

@sivaschenko sivaschenko self-assigned this Feb 11, 2019
@sivaschenko
Copy link
Member

Hi @suryakant-krish thanks for the update! This pull request contains much more changes than #19414, is it intentional? Also can you please check if test fixes applied to 2.3-develop PR should be applied to this pull request as well.

Finally, it would be great to squash changes into a single commit.

@sivaschenko
Copy link
Member

Closing this pull request due to inactivity, feel free to reopen if you'd like to continue progress on in

@ghost
Copy link

ghost commented Feb 21, 2019

Hi @suryakant-krish, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@amol2jcommerce
Copy link
Contributor

amol2jcommerce commented Feb 21, 2019 via email

@dipti2jcommerce
Copy link

dipti2jcommerce commented Feb 21, 2019 via email

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

Successfully merging this pull request may close these issues.

7 participants