Skip to content

Commit 32e0693

Browse files
author
shikhamis11
committed
#20893: Fixed #15059 Cannot reorder from the first try
0 parents  commit 32e0693

File tree

33,450 files changed

+3549777
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

33,450 files changed

+3549777
-0
lines changed

‎.github/.htaccess‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
<IfVersion < 2.4>
2+
Order deny,allow
3+
Deny from all
4+
</IfVersion>
5+
<IfVersion >= 2.4>
6+
Require all denied
7+
</IfVersion>

‎.github/CODE_OF_CONDUCT.md‎

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6+
7+
## Our Standards
8+
9+
Examples of behavior that contributes to creating a positive environment include:
10+
11+
* Using welcoming and inclusive language
12+
* Being respectful of differing viewpoints and experiences
13+
* Gracefully accepting constructive criticism
14+
* Focusing on what is best for the community
15+
* Showing empathy towards other community members
16+
17+
Examples of unacceptable behavior by participants include:
18+
19+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20+
* Trolling, insulting/derogatory comments, and personal or political attacks
21+
* Public or private harassment
22+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23+
* Other conduct which could reasonably be considered inappropriate in a professional setting
24+
25+
## Our Responsibilities
26+
27+
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28+
29+
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30+
31+
## Scope
32+
33+
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34+
35+
## Enforcement
36+
37+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38+
39+
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40+
41+
## Attribution
42+
43+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
44+
45+
[homepage]: http://contributor-covenant.org
46+
[version]: http://contributor-covenant.org/version/1/4/

‎.github/CONTRIBUTING.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# Contributing to Magento 2 code
2+
3+
Contributions to the Magento 2 codebase are done using the fork & pull model.
4+
This contribution model has contributors maintaining their own copy of the forked codebase (which can easily be synced with the main copy). The forked repository is then used to submit a request to the base repository to “pull” a set of changes. For more information on pull requests please refer to [GitHub Help](https://help.github.com/articles/about-pull-requests/).
5+
6+
Contributions can take the form of new components or features, changes to existing features, tests, documentation (such as developer guides, user guides, examples, or specifications), bug fixes or optimizations.
7+
8+
The Magento 2 development team will review all issues and contributions submitted by the community of developers in the first in, first out order. During the review we might require clarifications from the contributor. If there is no response from the contributor within two weeks, the pull request will be closed.
9+
10+
11+
## Contribution requirements
12+
13+
1. Contributions must adhere to the [Magento coding standards](https://devdocs.magento.com/guides/v2.2/coding-standards/bk-coding-standards.html).
14+
2. Pull requests (PRs) must be accompanied by a meaningful description of their purpose. Comprehensive descriptions increase the chances of a pull request being merged quickly and without additional clarification requests.
15+
3. Commits must be accompanied by meaningful commit messages. Please see the [Magento Pull Request Template](https://github.com/magento/magento2/blob/2.2-develop/.github/PULL_REQUEST_TEMPLATE.md) for more information.
16+
4. PRs which include bug fixes must be accompanied with a step-by-step description of how to reproduce the bug.
17+
3. PRs which include new logic or new features must be submitted along with:
18+
* Unit/integration test coverage
19+
* Proposed [documentation](https://devdocs.magento.com) updates. Documentation contributions can be submitted via the [devdocs GitHub](https://github.com/magento/devdocs).
20+
4. For larger features or changes, please [open an issue](https://github.com/magento/magento2/issues) to discuss the proposed changes prior to development. This may prevent duplicate or unnecessary effort and allow other contributors to provide input.
21+
5. All automated tests must pass (all builds on [Travis CI](https://travis-ci.org/magento/magento2) must be green).
22+
23+
## Contribution process
24+
25+
If you are a new GitHub user, we recommend that you create your own [free github account](https://github.com/signup/free). This will allow you to collaborate with the Magento 2 development team, fork the Magento 2 project and send pull requests.
26+
27+
1. Search current [listed issues](https://github.com/magento/magento2/issues) (open or closed) for similar proposals of intended contribution before starting work on a new contribution.
28+
2. Review the [Contributor License Agreement](https://magento.com/legaldocuments/mca) if this is your first time contributing.
29+
3. Create and test your work.
30+
4. Fork the Magento 2 repository according to the [Fork A Repository instructions](https://devdocs.magento.com/guides/v2.2/contributor-guide/contributing.html#fork) and when you are ready to send us a pull request – follow the [Create A Pull Request instructions](https://devdocs.magento.com/guides/v2.2/contributor-guide/contributing.html#pull_request).
31+
5. Once your contribution is received the Magento 2 development team will review the contribution and collaborate with you as needed.
32+
33+
## Code of Conduct
34+
35+
Please note that this project is released with a Contributor Code of Conduct. We expect you to agree to its terms when participating in this project.
36+
The full text is available in the repository [Wiki](https://github.com/magento/magento2/wiki/Magento-Code-of-Conduct).

‎.github/ISSUE_TEMPLATE.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
<!---
2+
Thank you for contributing to Magento.
3+
To help us process this issue we recommend that you add the following information:
4+
- Summary of the issue,
5+
- Information on your environment,
6+
- Steps to reproduce,
7+
- Expected and actual results,
8+
Fields marked with (*) are required. Please don't remove the template.
9+
10+
Please also have a look at our guidelines article before adding a new issue https://github.com/magento/magento2/wiki/Issue-reporting-guidelines
11+
-->
12+
13+
### Preconditions (*)
14+
<!---
15+
Please provide as detailed information about your environment as possible.
16+
For example Magento version, tag, HEAD, PHP & MySQL version, etc..
17+
-->
18+
1.
19+
2.
20+
21+
### Steps to reproduce (*)
22+
<!---
23+
It is important to provide a set of clear steps to reproduce this bug.
24+
If relevant please include code samples
25+
-->
26+
1.
27+
2.
28+
3.
29+
30+
### Expected result (*)
31+
<!--- Tell us what should happen -->
32+
1. [Screenshots, logs or description]
33+
34+
### Actual result (*)
35+
<!--- Tell us what happens instead -->
36+
1. [Screenshots, logs or description]

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
name: Bug report
3+
about: Technical issue with the Magento 2 core components
4+
5+
---
6+
7+
<!---
8+
Please review our guidelines before adding a new issue: https://github.com/magento/magento2/wiki/Issue-reporting-guidelines
9+
Fields marked with (*) are required. Please don't remove the template.
10+
-->
11+
12+
### Preconditions (*)
13+
<!---
14+
Provide the exact Magento version (example: 2.2.5) and any important information on the environment where bug is reproducible.
15+
-->
16+
1.
17+
2.
18+
19+
### Steps to reproduce (*)
20+
<!---
21+
Important: Provide a set of clear steps to reproduce this bug. We can not provide support without clear instructions on how to reproduce.
22+
-->
23+
1.
24+
2.
25+
26+
### Expected result (*)
27+
<!--- Tell us what do you expect to happen. -->
28+
1. [Screenshots, logs or description]
29+
2.
30+
31+
### Actual result (*)
32+
<!--- Tell us what happened instead. Include error messages and issues. -->
33+
1. [Screenshots, logs or description]
34+
2.

‎.github/ISSUE_TEMPLATE/developer-experience-issue.md‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
name: Developer experience issue
3+
about: Issues related to customization, extensibility, modularity
4+
5+
---
6+
7+
<!---
8+
Please review our guidelines before adding a new issue: https://github.com/magento/magento2/wiki/Issue-reporting-guidelines
9+
Fields marked with (*) are required. Please don't remove the template.
10+
-->
11+
12+
### Summary (*)
13+
<!--- Describe the issue you are experiencing. Include general information, error messages, environments, and so on. -->
14+
15+
### Examples (*)
16+
<!--- Provide code examples or a patch with a test (recommended) to clearly indicate the problem. -->
17+
18+
### Proposed solution
19+
<!--- Suggest your potential solutions for this issue. -->

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
name: Feature request
3+
about: Please consider reporting directly to https://github.com/magento/community-features
4+
5+
---
6+
7+
<!---
8+
Important: This repository is intended only for Magento 2 Technical Issues. Enter Feature Requests at https://github.com/magento/community-features. Project stakeholders monitor and manage requests. Feature requests entered using this form may be moved to the forum. Fields marked with (*) are required. Please don't remove the template.
9+
-->
10+
11+
### Description (*)
12+
<!--- Describe the feature you would like to add. -->
13+
14+
### Expected behavior (*)
15+
<!--- What is the expected behavior of this feature? How is it going to work? -->
16+
17+
### Benefits
18+
<!--- How do you think this feature would improve Magento? -->
19+
20+
### Additional information
21+
<!--- What other information can you provide about the desired feature? -->

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
<!---
2+
Thank you for contributing to Magento.
3+
To help us process this pull request we recommend that you add the following information:
4+
- Summary of the pull request,
5+
- Issue(s) related to the changes made,
6+
- Manual testing scenarios
7+
Fields marked with (*) are required. Please don't remove the template.
8+
-->
9+
10+
<!--- Please provide a general summary of the Pull Request in the Title above -->
11+
12+
### Description (*)
13+
<!---
14+
Please provide a description of the changes proposed in the pull request.
15+
Letting us know what has changed and why it needed changing will help us validate this pull request.
16+
-->
17+
18+
### Fixed Issues (if relevant)
19+
<!---
20+
If relevant, please provide a list of fixed issues in the format magento/magento2#<issue_number>.
21+
There could be 1 or more issues linked here and it will help us find some more information about the reasoning behind this change.
22+
-->
23+
1. magento/magento2#<issue_number>: Issue title
24+
2. ...
25+
26+
### Manual testing scenarios (*)
27+
<!---
28+
Please provide a set of unambiguous steps to test the proposed code change.
29+
Giving us manual testing scenarios will help with the processing and validation process.
30+
-->
31+
1. ...
32+
2. ...
33+
34+
### Contribution checklist (*)
35+
- [ ] Pull request has a meaningful description of its purpose
36+
- [ ] All commits are accompanied by meaningful commit messages
37+
- [ ] All new or changed code is covered with unit/integration tests (if applicable)
38+
- [ ] All automated tests passed successfully (all builds on Travis CI are green)

‎.gitignore‎

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
/.buildpath
2+
/.cache
3+
/.metadata
4+
/.project
5+
/.settings
6+
/.vscode
7+
atlassian*
8+
/nbproject
9+
/robots.txt
10+
/pub/robots.txt
11+
/sitemap
12+
/sitemap.xml
13+
/pub/sitemap
14+
/pub/sitemap.xml
15+
/.idea
16+
/.gitattributes
17+
/app/config_sandbox
18+
/app/etc/config.php
19+
/app/etc/env.php
20+
/app/code/Magento/TestModule*
21+
/lib/internal/flex/uploader/.actionScriptProperties
22+
/lib/internal/flex/uploader/.flexProperties
23+
/lib/internal/flex/uploader/.project
24+
/lib/internal/flex/uploader/.settings
25+
/lib/internal/flex/varien/.actionScriptProperties
26+
/lib/internal/flex/varien/.flexLibProperties
27+
/lib/internal/flex/varien/.project
28+
/lib/internal/flex/varien/.settings
29+
/node_modules
30+
/.grunt
31+
/Gruntfile.js
32+
/package.json
33+
/.php_cs
34+
/.php_cs.cache
35+
/grunt-config.json
36+
/pub/media/*.*
37+
!/pub/media/.htaccess
38+
/pub/media/attribute/*
39+
!/pub/media/attribute/.htaccess
40+
/pub/media/analytics/*
41+
/pub/media/catalog/*
42+
!/pub/media/catalog/.htaccess
43+
/pub/media/customer/*
44+
!/pub/media/customer/.htaccess
45+
/pub/media/downloadable/*
46+
!/pub/media/downloadable/.htaccess
47+
/pub/media/favicon/*
48+
/pub/media/import/*
49+
!/pub/media/import/.htaccess
50+
/pub/media/logo/*
51+
/pub/media/theme/*
52+
/pub/media/theme_customization/*
53+
!/pub/media/theme_customization/.htaccess
54+
/pub/media/wysiwyg/*
55+
!/pub/media/wysiwyg/.htaccess
56+
/pub/media/tmp/*
57+
!/pub/media/tmp/.htaccess
58+
/pub/media/captcha/*
59+
/pub/static/*
60+
!/pub/static/.htaccess
61+
62+
/var/*
63+
!/var/.htaccess
64+
/vendor/*
65+
!/vendor/.htaccess
66+
/generated/*
67+
!/generated/.htaccess
68+
.DS_Store

0 commit comments

Comments
 (0)