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
The Community Website is a centralized hub for showcasing open-source projects, connecting contributors, and fostering collaboration.
5
+
6
+
# 🚀 How to Contribute
7
+
8
+
We love contributions from everyone! Whether you're fixing a bug, adding a new feature, or improving documentation, your help is always appreciated. Here's how you can contribute:
3
9
4
10
Follow the steps below to contribute effectively:
5
11
6
-
1.**Fork the Repository:**
7
-
- Navigate to the `dev` branch and fork the repository onto your personal GitHub account.
12
+
1.**Fork the Repository:** Start by forking the repository to your own GitHub account.
8
13
9
-
2.**Clone the Repository:**
10
-
- Clone the forked repository to your local development environment.
- Before making any changes, create a new branch using the required naming convention:
17
-
```bash
18
-
git checkout -b feature/your-feature-name
19
-
```
20
-
**Branch Naming Schema:**`feature/your-feature-name` or `fix/your-bug-description`
17
+
3.**Create a New Branch Locally:** Create a branch for your feature or fix. Name your branch in a way that describes the purpose of your changes. For example:
18
+
-`feature/feature-name`
19
+
-`bugfix/bug-description`
20
+
-`docs/clarify-setup-instructions`
21
21
22
22
4.**Make Your Changes:**
23
23
- Add your code, features, or bug fixes.
24
24
25
-
5.**Commit Your Changes:**
26
-
- Commit your changes locally with meaningful messages:
27
-
```bash
28
-
git add .
29
-
git commit -m "feat: Added new feature"
30
-
```
25
+
5.**Commit Guidelines:** When committing changes to your branch, please follow this naming scheme to keep commit history clean and readable:
refactor: Code changes that neither fix a bug nor add a feature, but improve the structure.
36
+
test: Adding or modifying tests.
37
+
chore: Changes to the build process or auxiliary tools.
37
38
38
-
7.**Create a Pull Request (PR):**
39
-
- Go to the community repository and create a PR from your local branch to the `dev` branch.
39
+
Example Commit Messages:
40
40
41
-
8.**Code Review:**
42
-
- Your PR will be reviewed by maintainers. Make necessary changes if requested.
41
+
feat: add user authentication to the website
42
+
fix: resolve issue with missing image on homepage
43
+
docs: update README.md with contribution guidelines
44
+
style: format code according to ESLint rules
45
+
test: add unit test for login function
46
+
chore: update dependencies to latest version
47
+
48
+
6.**Push and Create a Pull Request:** Once you're ready, push your changes to your forked repository and open a pull request to the `dev` repository.
49
+
50
+
8.**Follow Up** We will review your changes and may provide feedback. Please address any comments or requested changes, and we’ll merge your contribution!
43
51
44
52
---
45
53
@@ -53,12 +61,5 @@ Follow the steps below to contribute effectively:
53
61
54
62
Thank you for being a valuable part of our community! 🎉
55
63
56
-
57
-
58
-
59
-
<ahref="https://discord.gg/X69MUr2DKm"title="Discord server invite link"><imgsrc="https://freelogopng.com/images/all_img/1691730767discord-logo-transparent.png"width="100"></a>
Join our Discord community for more discussions and updates!
65
+
<ahref="https://discord.gg/X69MUr2DKm"title="Discord server invite link"><imgsrc="https://freelogopng.com/images/all_img/1691730767discord-logo-transparent.png"width="25"></a>
0 commit comments