Skip to content

Commit d0506af

Browse files
authored
Merge pull request #23 from KamilAdd-Byte/develop
Develop
2 parents fa678d6 + 1e2d393 commit d0506af

File tree

1 file changed

+75
-0
lines changed

1 file changed

+75
-0
lines changed

CONTRIBUTING.md

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
# Contributing to Commit-Craft
2+
3+
Thank you for your interest in contributing to Commit-Craft! Contributing to an open-source project is a fantastic way to learn, share knowledge, and build a community. Below are the guidelines to help you contribute effectively.
4+
5+
## How Can You Help?
6+
7+
### 1. Reporting Issues
8+
9+
If you’ve found a bug, have an idea for a new feature, or noticed something that needs improvement, please report it in the [Issues]:(LINK_TO_ISSUES) section.
10+
11+
When reporting an issue, try to include:
12+
- A detailed description of the problem.
13+
- Steps to reproduce the issue (if applicable).
14+
- Information about your environment (software version, operating system, etc.).
15+
16+
### 2. Proposing New Features
17+
18+
Would you like to add a new feature? You can also submit a proposal in the [Issues](https://github.com/KamilAdd-Byte/commit-craft/issues); section. Please include details such as:
19+
- What value the feature will bring.
20+
- Examples of how it might be used.
21+
22+
### 3. Creating Pull Requests
23+
24+
If you’d like to make changes to the code directly, follow these steps:
25+
26+
1. **Fork the repository**:
27+
Click the "Fork" button at the top of the repository page.
28+
29+
2. **Clone the repository to your local machine**:
30+
```bash
31+
git clone https://github.com/KamilAdd-Byte/commit-craft.git
32+
```
33+
34+
3. **Create a branch**:
35+
Before starting your work, create a new branch:
36+
```bash
37+
git checkout -b <number-issue>feature-name
38+
```
39+
40+
4. **Make your changes**:
41+
Edit the code, add new features, or fix bugs.
42+
43+
5. **Update the documentation**:
44+
Ensure that your changes are appropriately documented.
45+
46+
6. **Run tests**:
47+
Before submitting changes, verify that everything works correctly and that all tests pass.
48+
49+
7. **Push your changes**:
50+
Use [Conventional Commits](https://www.conventionalcommits.org/) to format your commit messages. For example:
51+
```bash
52+
git add .
53+
git commit -m "[Number-issue]feat: add new feature description"
54+
git push origin <number-issue>feature-name
55+
```
56+
57+
8. **Create a Pull Request (PR)**:
58+
Go to your fork’s page and click "New Pull Request."
59+
60+
When creating the PR:
61+
- Describe what you changed.
62+
- Explain why the changes are necessary.
63+
64+
## Code Guidelines
65+
66+
- Follow the [coding standard].
67+
- Add comments to make the code more understandable.
68+
- Write tests for new features.
69+
- Avoid making large changes in a single PR; instead, split them into smaller parts.
70+
71+
## Communication
72+
73+
- If you have questions, you can post them in the [Discussions](https://github.com/KamilAdd-Byte/commit-craft/discussions) section or email us at [[email protected]].
74+
75+
Thank you for your time and effort. Together, we can build something amazing! 🎉

0 commit comments

Comments
 (0)