You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: .github/CONTRIBUTING.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ The Magento 2 development team will review all issues and contributions submitte
16
16
4. PRs which include bug fixes must be accompanied with a step-by-step description of how to reproduce the bug.
17
17
3. PRs which include new logic or new features must be submitted along with:
18
18
* Unit/integration test coverage
19
-
* Proposed [documentation](http://devdocs.magento.com) updates. Documentation contributions can be submitted via the [devdocs GitHub](https://github.com/magento/devdocs).
19
+
* Proposed [documentation](https://devdocs.magento.com) updates. Documentation contributions can be submitted via the [devdocs GitHub](https://github.com/magento/devdocs).
20
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
21
5. All automated tests must pass (all builds on [Travis CI](https://travis-ci.org/magento/magento2) must be green).
22
22
@@ -27,7 +27,7 @@ If you are a new GitHub user, we recommend that you create your own [free github
27
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
28
2. Review the [Contributor License Agreement](https://magento.com/legaldocuments/mca) if this is your first time contributing.
29
29
3. Create and test your work.
30
-
4. Fork the Magento 2 repository according to the [Fork A Repository instructions](http://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](http://devdocs.magento.com/guides/v2.2/contributor-guide/contributing.html#pull_request).
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
31
5. Once your contribution is received the Magento 2 development team will review the contribution and collaborate with you as needed.
Copy file name to clipboardexpand all lines: CHANGELOG.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ To get detailed information about changes in Magento 2.3.0, see the [Release Not
4
4
5
5
2.1.0
6
6
=============
7
-
To get detailed information about changes in Magento 2.1.0, please visit [Magento Community Edition (CE) Release Notes](http://devdocs.magento.com/guides/v2.1/release-notes/ReleaseNotes2.1.0CE.html"Magento Community Edition (CE) Release Notes")
7
+
To get detailed information about changes in Magento 2.1.0, please visit [Magento Community Edition (CE) Release Notes](https://devdocs.magento.com/guides/v2.1/release-notes/ReleaseNotes2.1.0CE.html"Magento Community Edition (CE) Release Notes")
8
8
9
9
2.0.0
10
10
=============
@@ -1025,7 +1025,7 @@ Tests:
1025
1025
* Improved backend menu keyboard accessibility
1026
1026
* Accessibility improvements: WAI-ARIA in a product item on a category page and related products
1027
1027
* Checkout flow code can work with a separate DB storage
1028
-
* <ahref="http://devdocs.magento.com/guides/v1.0/release-notes/changes.html#change-devrc-unit">Unit tests moved to module directories</a>
1028
+
* <ahref="https://devdocs.magento.com/guides/v1.0/release-notes/changes.html#change-devrc-unit">Unit tests moved to module directories</a>
1029
1029
* Addressed naming inconsistencies in REST routes
1030
1030
* Added Advanced Developer workflow for frontend developers
Copy file name to clipboardexpand all lines: app/code/Magento/Analytics/README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Magento_Analytics Module
2
2
3
-
The Magento_Analytics module integrates your Magento instance with the [Magento Business Intelligence (MBI)](https://magento.com/products/business-intelligence) to use [Advanced Reporting](http://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html) functionality.
3
+
The Magento_Analytics module integrates your Magento instance with the [Magento Business Intelligence (MBI)](https://magento.com/products/business-intelligence) to use [Advanced Reporting](https://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html) functionality.
4
4
5
5
The module implements the following functionality:
6
6
@@ -16,8 +16,8 @@ The module implements the following functionality:
16
16
17
17
## Structure
18
18
19
-
Beyond the [usual module file structure](http://devdocs.magento.com/guides/v2.2/architecture/archi_perspectives/components/modules/mod_intro.html) the module contains a directory `ReportXml`.
20
-
[Report XML](http://devdocs.magento.com/guides/v2.2/advanced-reporting/report-xml.html) is a markup language used to build reports for Advanced Reporting.
19
+
Beyond the [usual module file structure](https://devdocs.magento.com/guides/v2.2/architecture/archi_perspectives/components/modules/mod_intro.html) the module contains a directory `ReportXml`.
20
+
[Report XML](https://devdocs.magento.com/guides/v2.2/advanced-reporting/report-xml.html) is a markup language used to build reports for Advanced Reporting.
21
21
The language declares SQL queries using XML declaration.
The Magento_CatalogAnalytics module configures data definitions for a data collection related to the Catalog module entities to be used in [Advanced Reporting](http://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html).
3
+
The Magento_CatalogAnalytics module configures data definitions for a data collection related to the Catalog module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html).
The Magento_CustomerAnalytics module configures data definitions for a data collection related to the Customer module entities to be used in [Advanced Reporting](http://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html).
3
+
The Magento_CustomerAnalytics module configures data definitions for a data collection related to the Customer module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html).
Copy file name to clipboardexpand all lines: app/code/Magento/InstantPurchase/README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Prerequisites to display the Instant Purchase button:
10
10
11
11
## Structure
12
12
13
-
In addition to [a typical file structure for a Magento 2 module](http://devdocs.magento.com/guides/v2.2/extension-dev-guide/build/module-file-structure.html)`PaymentMethodsIntegration` directory contains interfaces and basic implementation of integration vault payment method to the instant purchase.
13
+
In addition to [a typical file structure for a Magento 2 module](https://devdocs.magento.com/guides/v2.2/extension-dev-guide/build/module-file-structure.html)`PaymentMethodsIntegration` directory contains interfaces and basic implementation of integration vault payment method to the instant purchase.
14
14
15
15
## Extensibility
16
16
@@ -22,7 +22,7 @@ All payments created for instant purchase also have `'instant-purchase' => true`
22
22
23
23
### Payment method integration
24
24
25
-
Instant purchase support may be implemented for any payment method with [vault support](http://devdocs.magento.com/guides/v2.1/payments-integrations/vault/vault-intro.html).
25
+
Instant purchase support may be implemented for any payment method with [vault support](https://devdocs.magento.com/guides/v2.1/payments-integrations/vault/vault-intro.html).
26
26
Basic implementation provided in `Magento\InstantPurchase\PaymentMethodIntegration` should be enough in most cases. It is not enabled by default to avoid issues on production sites and authors of vault payment method should verify correct work for instant purchase manually.
27
27
To enable basic implementation just add single option to configuration of payemnt method in `config.xml`:
28
28
@@ -52,7 +52,7 @@ Basic implementation is a good start point but it's recommended to provide own i
52
52
53
53
The `Magento_InstantPurchase` module does not introduce backward incompatible changes.
54
54
55
-
You can track [backward incompatible changes in patch releases](http://devdocs.magento.com/guides/v2.2/release-notes/changes/ce_changes.html).
55
+
You can track [backward incompatible changes in patch releases](https://devdocs.magento.com/guides/v2.2/release-notes/changes/ce_changes.html).
The Magento_QuoteAnalytics module configures data definitions for a data collection related to the Quote module entities to be used in [Advanced Reporting](http://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html).
3
+
The Magento_QuoteAnalytics module configures data definitions for a data collection related to the Quote module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html).
0 commit comments