Skip to content

Commit 440d012

Browse files
authored
Merge branch '1.9.4.x' into getAttributeRawValue-empty
2 parents 9b15887 + 9182521 commit 440d012

File tree

12,998 files changed

+260145
-1520973
lines changed

Some content is hidden

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

12,998 files changed

+260145
-1520973
lines changed

.all-contributorsrc

+1,379
Large diffs are not rendered by default.

.ddev/commands/web/php-cs-fixer

+7
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
#!/bin/bash
2+
3+
## Description: run PHP-CS-Fixer
4+
## Usage: php-cs-fixer
5+
## Example: ddev php-cs-fixer <path-to-files>
6+
7+
php vendor/bin/php-cs-fixer fix "$@"

.ddev/commands/web/phpcbf

+7
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
#!/bin/bash
2+
3+
## Description: run PHPCodeBeautifier
4+
## Usage: phpcbf
5+
## Example: ddev phpcbf <path-to-files>
6+
7+
php vendor/bin/phpcbf -s -p --report=full,source,summary "$@"

.ddev/commands/web/phpcs

+7
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
#!/bin/bash
2+
3+
## Description: run PHPCodeSniffer
4+
## Usage: phpcs
5+
## Example: ddev phpcs <path-to-files>
6+
7+
php vendor/bin/phpcs -s -p --report=full,summary "$@"

.ddev/commands/web/phpmd

+7
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
#!/bin/bash
2+
3+
## Description: run PHPMD
4+
## Usage: phpmd
5+
## Example: ddev phpmd <path-to-files>
6+
7+
php vendor/bin/phpmd "$@" text .phpmd.dist.xml

.ddev/commands/web/phpstan

+7
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
#!/bin/bash
2+
3+
## Description: run PHPStan
4+
## Usage: phpstan
5+
## Example: ddev phpstan <path-to-files>
6+
7+
XDEBUG_MODE=off php vendor/bin/phpstan analyze "$@"

.ddev/commands/web/rector

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
#!/bin/bash
2+
3+
## Description: run rector
4+
## Usage: rector
5+
## Example: ddev rector <path-to-files>
6+
7+
cp -n vendor/sreichel/openmage-rector/rector.php rector.php
8+
php vendor/bin/rector process "$@"
File renamed without changes.
File renamed without changes.

.github/ISSUE_TEMPLATE/bug_report.md

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
name: Bug report
3+
about: Technical issue with the OpenMage LTS core components
4+
title: ''
5+
labels: bug
6+
assignees: ''
7+
8+
---
9+
10+
<!---
11+
Fields marked with (*) are required. Please don't remove the template.
12+
-->
13+
14+
### Preconditions (*)
15+
<!---
16+
Provide the exact OpenMage version (example: 19.4.3) and any important information on the environment where bug is reproducible.
17+
-->
18+
1.
19+
2.
20+
21+
### Steps to reproduce (*)
22+
<!---
23+
Important: Provide a set of clear steps to reproduce this bug. We can not provide support without clear instructions on how to reproduce.
24+
-->
25+
1.
26+
2.
27+
28+
### Expected result (*)
29+
<!--- Tell us what do you expect to happen. -->
30+
1. [Screenshots, logs or description]
31+
2.
32+
33+
### Actual result (*)
34+
<!--- Tell us what happened instead. Include error messages and issues. -->
35+
1. [Screenshots, logs or description]
36+
2.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
name: Developer experience issue
3+
about: Issues related to customization, extensibility, modularity
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
<!---
11+
Fields marked with (*) are required. Please don't remove the template.
12+
-->
13+
14+
### Summary (*)
15+
<!--- Describe the issue you are experiencing. Include general information, error messages, environments, and so on. -->
16+
17+
### Examples (*)
18+
<!--- Provide code examples or a patch with a test (recommended) to clearly indicate the problem. -->
19+
20+
### Proposed solution
21+
<!--- Suggest your potential solutions for this issue. -->
+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: New Feature
6+
assignees: ''
7+
8+
---
9+
10+
<!---
11+
Fields marked with (*) are required. Please don't remove the template.
12+
-->
13+
14+
### Description (*)
15+
<!--- Describe the feature you would like to add. -->
16+
17+
### Expected behavior (*)
18+
<!--- What is the expected behavior of this feature? How is it going to work? -->
19+
20+
### Benefits
21+
<!--- How do you think this feature would improve Magento? -->
22+
23+
### Additional information
24+
<!--- What other information can you provide about the desired feature? -->

.github/PULL_REQUEST_TEMPLATE.md

+53
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
<!---
2+
Thank you for contributing to OpenMage LTS.
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+
### Related Pull Requests
19+
<!-- related pull request placeholder -->
20+
21+
### Fixed Issues (if relevant)
22+
<!---
23+
If relevant, please provide a list of fixed issues in the format OpenMage/magento-lts#<issue_number>.
24+
There could be 1 or more issues linked here and it will help us find some more information about the reasoning behind this change.
25+
-->
26+
1. Fixes OpenMage/magento-lts#<issue_number>
27+
28+
### Manual testing scenarios (*)
29+
<!---
30+
Please provide a set of unambiguous steps to test the proposed code change.
31+
Giving us manual testing scenarios will help with the processing and validation process.
32+
-->
33+
1. ...
34+
2. ...
35+
36+
### Questions or comments
37+
<!---
38+
If relevant, here you can ask questions or provide comments on your pull request for the reviewer
39+
For example if you need assistance with writing tests or would like some feedback on one of your development ideas
40+
-->
41+
42+
### Contribution checklist (*)
43+
- [ ] Pull request has a meaningful description of its purpose
44+
- [ ] All commits are accompanied by meaningful commit messages
45+
- [ ] All automated tests passed successfully (all builds are green)
46+
- [ ] Add yourself to contributors list
47+
<!---
48+
Install: `yarn add --dev all-contributors-cli`
49+
Add yourself: `yarn all-contributors add @YOUR_NAME <types>`
50+
This updates `.all-contributorsrc, README.md` and commits this changes automatically
51+
contribution types: code, doc, design
52+
See other contributions type at https://allcontributors.org/docs/en/emoji-key
53+
-->

.github/SECURITY.md

+29
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
# Security Policy
2+
3+
OpenMage LTS is a fork of Magento CE 1.9 which provides a place for the Magento community to continue to contribute to the Magento 1 code base. We appreciate you disclosing important security vulnerabilities responsibly and privately by following the easy process defined below.
4+
5+
We will keep the details of your security vulnerability report private and only share it with verified members of our organization or our partner organizations and only on an as-needed basis.
6+
7+
## Supported Versions
8+
9+
| OpenMage LTS Tag | Magento Version | Branch | Supported |
10+
| -------------------- | ----------------- | ---------------- | ------------------ |
11+
| ~20.0.4 | 1.9.4.5 | 20.0 | :white_check_mark: |
12+
| ~19.4.8 | 1.9.4.5 | 1.9.4.x | :white_check_mark: |
13+
| - | <= 1.9.4.4 | multiple | :x: |
14+
15+
## Reporting a Vulnerability
16+
17+
To report a vulnerability, please *DO NOT* open a public Issue or Pull Request.
18+
19+
Please email your security vulnerability report to security@openmage.org along with your Github user name so that once we create a security advisory you may be added to it as a collaborator for further review.
20+
21+
We will review the advisory and work with you to find a suitable solution. We will publicly disclose the vulnerability once a patch is prepared and our community and partners have an easy path forward to apply the patch promptly. We will be sure to give you credit for the vulnerability discovery unless you request otherwise.
22+
23+
## Limitation of Liability
24+
25+
As per section 8 of the [OSL 3.0 license](https://opensource.org/licenses/OSL-3.0) by which this source code is made available to the general public, we offer this source code only on a "use at your own risk" basis.
26+
27+
> 8) Limitation of Liability. Under no circumstances and under no legal theory, whether in tort (including negligence), contract, or otherwise, shall the Licensor be liable to anyone for any indirect, special, incidental, or consequential damages of any character arising as a result of this License or the use of the Original Work including, without limitation, damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses. This limitation of liability shall not apply to the extent applicable law prohibits such limitation.
28+
29+
For the full text see `LICENSE.md`.

0 commit comments

Comments
 (0)