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: docs/CONTRIBUTING.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -59,16 +59,16 @@ The Magento 2 development team will review all issues and contributions submitte
59
59
4. PRs which include bug fixing, must be accompanied with step-by-step description of how to reproduce the bug.
60
60
3. PRs which include new logic or new features must be submitted along with:
61
61
* Unit/integration test coverage where applicable.
62
-
* Updated documentation in the module directory `app/code/PageBuilder/docs`.
63
-
4. 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
-
5. All automated tests are passed successfully locally. After PR submitted Magento team will run builds on continuous integration environment.
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.
65
65
66
66
## Contribution process
67
67
68
68
If you are a new GitHub user, we recommend that you create your own [free github account](https://github.com/signup/free). By doing that, you will be able to collaborate with the Magento 2 development team, “fork” the Magento 2 project and be able to easily send “pull requests”.
69
69
70
70
1. Search current [listed issues](https://github.com/magento/magento2-page-builder/issues) on GitHub (open or closed) and [list of known issues](roadmap.md#Known Issues) on our roadmap for similar proposals of intended contribution before starting work on a new contribution.
71
-
2. Please contact us in Slack chanel if you want to work on issue from [list of known issues](roadmap.md#Known Issues).
71
+
2. Please contact us in Slack channel if you want to work on issue from [list of known issues](roadmap.md#Known Issues).
72
72
2. Review the [Contributor License Agreement](https://magento.com/legaldocuments/mca) if this is your first time contributing.
73
73
3. Create and test your work.
74
74
4. Fork the Magento 2 repository according to [Fork a repository instructions](http://devdocs.magento.com/guides/v2.0/contributor-guide/contributing.html#fork) and when you are ready to send us a pull request – follow [Create a pull request instructions](http://devdocs.magento.com/guides/v2.0/contributor-guide/contributing.html#pull_request). Instructions written for `https://github.com/magento/magento2` repository, but they also apply to `https://github.com/magento/magento2-page-builder`.
All events starting with `contentType:` can also be called for specific content types by prefixing the content types name (`{{name}}:{{event}}`) like the following:
0 commit comments