Skip to content

Commit 7140eb9

Browse files
Merge pull request #49 from riconeitzel/patch-1
Update how-to-contribute-to-the-magento-2-community.md
2 parents 80a91d9 + 1d08b7d commit 7140eb9

File tree

1 file changed

+21
-21
lines changed

1 file changed

+21
-21
lines changed

how-to-contribute-to-the-magento-2-community.md

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,48 +1,48 @@
1-
# Contributing to the Magento 2 Community
1+
# Contributing to the Mage-OS Community
22

33
[TOC]
44

55
## Introduction
66

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
88
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
1010
environment to submitting your contributions for review.
1111

1212
## Prerequisites
1313

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:
1515

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
1717
stable version.
1818
2. **Git**: Install Git on your machine to help manage your code changes.
1919
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.
2121

22-
## Clone the Magento 2 Repository
22+
## Clone the Mage-OS Repository
2323

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
2525
machine. Follow these steps to get started:
2626

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.
2828
2. Run the following command to clone the repository:
2929

3030
```shell
31-
git clone https://github.com/magento/magento2.git
31+
git clone git@github.com:mage-os/mageos-magento2.git
3232
```
3333

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:
3535

3636
```shell
37-
cd magento2
37+
cd mageos-magento2
3838
```
3939

4040
## Creating a Branch
4141

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.
4343
This ensures that your changes are isolated and can be easily managed. Follow these steps to create a new branch:
4444

45-
1. Ensure that you are in the `magento2` directory.
45+
1. Ensure that you are in the `mageos-magento2` directory.
4646
2. Run the following command to create a new branch:
4747

4848
```shell
@@ -62,7 +62,7 @@ are a few examples:
6262
If you want to fix a bug, follow these steps:
6363

6464
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.
6666
3. Make the necessary changes to address the bug.
6767
4. Test your changes to ensure they fix the bug and do not introduce any regressions.
6868

@@ -77,10 +77,10 @@ If you want to develop a new feature, follow these steps:
7777

7878
## Running Tests
7979

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
8181
your changes do not introduce any regressions. Follow these steps to run the tests:
8282

83-
1. Ensure that you are in the `magento2` directory.
83+
1. Ensure that you are in the `mageos-magento2` directory.
8484
2. Run the following command to install the necessary testing dependencies:
8585

8686
```shell
@@ -106,8 +106,8 @@ Follow these steps to create a pull request (PR) on GitHub:
106106
git push origin my-branch-name
107107
```
108108

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).
111111
3. Click on the "Pull requests" tab.
112112
4. Click on the "New pull request" button.
113113
5. Select your branch from the dropdown menu.
@@ -116,7 +116,7 @@ git push origin my-branch-name
116116

117117
## Conclusion
118118

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
121121
ecosystem. Remember to always adhere to best practices, thoroughly test your changes, and actively engage with the
122122
community for feedback and guidance. Happy contributing!

0 commit comments

Comments
 (0)