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
[Add image uploader to content type]: image-uploader.md
41
-
[Roadmap and Known Issues]: roadmap.md
42
-
[How to create custom PageBuilder content type container]: how-to-create-custom-content-type-container.md
43
-
<!-- {% endcomment %} -->
44
3
## Overview
45
4
46
5
Contributions to the Magento 2 codebase are done using the fork & pull model.
@@ -50,18 +9,17 @@ Contributions can take the form of new components/features, changes to existing
50
9
51
10
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 for two weeks, the issue is closed.
52
11
53
-
54
12
## Contribution requirements
55
13
56
14
1. Contributions must adhere to [Magento coding standards](http://devdocs.magento.com/guides/v2.0/coding-standards/bk-coding-standards.html).
57
15
2. Pull requests (PRs) must be accompanied by a meaningful description of their purpose. Comprehensive descriptions increase the chances of a pull request to be merged quickly and without additional clarification requests.
58
16
3. Commits must be accompanied by meaningful commit messages.
59
17
4. PRs which include bug fixing, must be accompanied with step-by-step description of how to reproduce the bug.
60
-
3. PRs which include new logic or new features must be submitted along with:
61
-
* Unit/integration test coverage where applicable.
62
-
* Updated documentation in the `docs` directory at the root level.
63
-
1. For large features or changes, please [open an issue](https://github.com/magento/magento2/issues) and discuss first. This may prevent duplicate or unnecessary effort, and it may gain you some additional contributors.
64
-
2. All automated tests are passed successfully locally. After PR submitted Magento team will run builds on continuous integration environment.
18
+
5. PRs which include new logic or new features must be submitted along with:
19
+
* Unit/integration test coverage where applicable.
20
+
* Updated documentation in the `docs` directory at the root level.
21
+
6. For large features or changes, please [open an issue](https://github.com/magento/magento2/issues) and discuss first. This may prevent duplicate or unnecessary effort, and it may gain you some additional contributors.
22
+
7. All automated tests are passed successfully locally. After PR submitted Magento team will run builds on continuous integration environment.
0 commit comments