Skip to content

Commit 2469595

Browse files
authored
Merge pull request #2 from SourcewareLab/docs/update-readme
docs: Update readme.md
2 parents de9eeb5 + 9f30a88 commit 2469595

File tree

1 file changed

+39
-38
lines changed

1 file changed

+39
-38
lines changed

README.md

Lines changed: 39 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -1,45 +1,53 @@
1+
# Community Website
2+
# 🤖 About
13

2-
# 🚀 Contribution Workflow
4+
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:
39

410
Follow the steps below to contribute effectively:
511

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.
813

9-
2. **Clone the Repository:**
10-
- Clone the forked repository to your local development environment.
11-
```bash
12-
git clone https://github.com/your-username/community-website.git
13-
```
14+
2. **Clone the Repository:** Clone the forked repository to your local development environment.<br><br>
15+
`git clone https://github.com/your-username/community-website.git`
1416

15-
3. **Create a New Branch Locally:**
16-
- 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`
2121

2222
4. **Make Your Changes:**
2323
- Add your code, features, or bug fixes.
2424

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:
26+
27+
Commit message format: `<type>:<short-description>`
28+
29+
Types:
3130

32-
6. **Push to Your Repository:**
33-
- Push the changes to your forked repository:
34-
```bash
35-
git push origin feature/your-feature-name
36-
```
31+
feat: A new feature or functionality added to the project.
32+
fix: A bug fix.
33+
docs: Documentation changes.
34+
style: Code style changes (e.g., formatting, missing semicolons).
35+
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.
3738

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

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!
4351

4452
---
4553

@@ -53,12 +61,5 @@ Follow the steps below to contribute effectively:
5361

5462
Thank you for being a valuable part of our community! 🎉
5563

56-
57-
58-
59-
<a href="https://discord.gg/X69MUr2DKm" title="Discord server invite link"><img src="https://freelogopng.com/images/all_img/1691730767discord-logo-transparent.png" width="100"></a>
60-
61-
![SourcewareLab Logo](https://raw.githubusercontent.com/SourcewareLab/community-website/refs/heads/main/imgs/logo.png)
62-
63-
64-
64+
Join our Discord community for more discussions and updates!
65+
<a href="https://discord.gg/X69MUr2DKm" title="Discord server invite link"><img src="https://freelogopng.com/images/all_img/1691730767discord-logo-transparent.png" width="25"></a>

0 commit comments

Comments
 (0)