1
- # Contributing to the Magento 2 Community
1
+ # Contributing to the Mage-OS Community
2
2
3
3
[ TOC]
4
4
5
5
## Introduction
6
6
7
- Thank you for your interest in contributing to the vibrant Magento 2 community! Your contributions can help improve the
7
+ Thank you for your interest in contributing to the vibrant Mage-OS community! Your contributions can help improve the
8
8
platform, fix bugs, develop new features, and enhance the overall user experience. This guide will walk you through the
9
- process of contributing to the Magento 2 community, covering everything from setting up your local development
9
+ process of contributing to the Mage-OS community, covering everything from setting up your local development
10
10
environment to submitting your contributions for review.
11
11
12
12
## Prerequisites
13
13
14
- Before you start contributing to the Magento 2 community, ensure that you have the following prerequisites in place:
14
+ Before you start contributing to the Mage-OS community, ensure that you have the following prerequisites in place:
15
15
16
- 1 . ** Magento 2 instance** : Set up a local development environment with a Magento 2 instance, preferably the latest
16
+ 1 . ** Mage-OS instance** : Set up a local development environment with a Mage-OS instance, preferably the latest
17
17
stable version.
18
18
2 . ** Git** : Install Git on your machine to help manage your code changes.
19
19
3 . ** GitHub Account** : Create an account on GitHub if you don't already have one. This will enable you to contribute to
20
- the Magento 2 repository.
20
+ the Mage-OS repository.
21
21
22
- ## Clone the Magento 2 Repository
22
+ ## Clone the Mage-OS Repository
23
23
24
- To contribute to the Magento 2 community, you will need to clone the official Magento 2 repository onto your local
24
+ To contribute to the Mage-OS community, you will need to clone the official Mage-OS repository onto your local
25
25
machine. Follow these steps to get started:
26
26
27
- 1 . Open your command line interface and navigate to the directory where you want to clone the Magento 2 repository.
27
+ 1 . Open your command line interface and navigate to the directory where you want to clone the Mage-OS repository.
28
28
2 . Run the following command to clone the repository:
29
29
30
30
``` shell
31
- git clone https:// github.com/magento/ magento2.git
31
+ git clone git@ github.com:mage-os/mageos- magento2.git
32
32
```
33
33
34
- 3 . Once the cloning process completes, navigate into the ` magento2 ` directory using the following command:
34
+ 3 . Once the cloning process completes, navigate into the ` mageos- magento2` directory using the following command:
35
35
36
36
``` shell
37
- cd magento2
37
+ cd mageos- magento2
38
38
```
39
39
40
40
## Creating a Branch
41
41
42
- Before you start making changes to the Magento 2 codebase, it's important to create a new branch for your contributions.
42
+ Before you start making changes to the Mage-OS codebase, it's important to create a new branch for your contributions.
43
43
This ensures that your changes are isolated and can be easily managed. Follow these steps to create a new branch:
44
44
45
- 1 . Ensure that you are in the ` magento2 ` directory.
45
+ 1 . Ensure that you are in the ` mageos- magento2` directory.
46
46
2 . Run the following command to create a new branch:
47
47
48
48
``` shell
@@ -62,7 +62,7 @@ are a few examples:
62
62
If you want to fix a bug, follow these steps:
63
63
64
64
1 . Identify the bug you want to fix.
65
- 2 . Navigate to the relevant file(s) in the Magento 2 codebase.
65
+ 2 . Navigate to the relevant file(s) in the Mage-OS codebase.
66
66
3 . Make the necessary changes to address the bug.
67
67
4 . Test your changes to ensure they fix the bug and do not introduce any regressions.
68
68
@@ -77,10 +77,10 @@ If you want to develop a new feature, follow these steps:
77
77
78
78
## Running Tests
79
79
80
- Before submitting your code changes for review, it is essential to run the tests provided by Magento 2 to ensure that
80
+ Before submitting your code changes for review, it is essential to run the tests provided by Mage-OS to ensure that
81
81
your changes do not introduce any regressions. Follow these steps to run the tests:
82
82
83
- 1 . Ensure that you are in the ` magento2 ` directory.
83
+ 1 . Ensure that you are in the ` mageos- magento2` directory.
84
84
2 . Run the following command to install the necessary testing dependencies:
85
85
86
86
``` shell
@@ -106,8 +106,8 @@ Follow these steps to create a pull request (PR) on GitHub:
106
106
git push origin my-branch-name
107
107
```
108
108
109
- 2 . Visit the official Magento 2 repository on
110
- GitHub: [ https://github.com/magento/ magento2 ] ( https://github.com/magento/ magento2 ) .
109
+ 2 . Visit the official Mage-OS repository on
110
+ GitHub: [ https://github.com/mage-os/mageos- magento2 ] ( https://github.com/mage-os/mageos- magento2 ) .
111
111
3 . Click on the "Pull requests" tab.
112
112
4 . Click on the "New pull request" button.
113
113
5 . Select your branch from the dropdown menu.
@@ -116,7 +116,7 @@ git push origin my-branch-name
116
116
117
117
## Conclusion
118
118
119
- Contributing to the Magento 2 community is an excellent way to improve the platform and collaborate with other
120
- developers. By following the steps outlined in this guide, you can start making a positive impact on the Magento 2
119
+ Contributing to the Mage-OS community is an excellent way to improve the platform and collaborate with other
120
+ developers. By following the steps outlined in this guide, you can start making a positive impact on the Mage-OS
121
121
ecosystem. Remember to always adhere to best practices, thoroughly test your changes, and actively engage with the
122
122
community for feedback and guidance. Happy contributing!
0 commit comments