|
1 |
| -Hereβs a set of **Contribution Guidelines** tailored for your open-source project: |
| 1 | +# Contributing to AI-health-chatbot |
2 | 2 |
|
3 |
| ---- |
| 3 | +Thank you for considering contributing to AI-health-chatbot! π |
| 4 | +We welcome contributions of all types β bug fixes, feature implementations, documentation improvements, and feedback. |
4 | 5 |
|
5 |
| -# Contribution Guidelines |
| 6 | +-> These guidelines are here to make the process smooth and collaborative for everyone. |
6 | 7 |
|
7 |
| -Thank you for considering contributing to **Blok**! We welcome contributions of all types, including bug fixes, feature implementations, documentation improvements, and feedback. These guidelines are here to make the process clear and smooth for everyone. |
| 8 | +## π How to Contribute |
8 | 9 |
|
9 |
| ---- |
| 10 | +### 1. Discuss Your Idea |
10 | 11 |
|
11 |
| -## How to Contribute |
| 12 | +* Before starting work on a major change, please open an **issue** in the repository. |
| 13 | +* Use the issue template (if available) or describe your idea clearly. |
12 | 14 |
|
13 |
| -### 1. **Discuss Your Idea** |
14 |
| -- Before starting work on a major change, please open an issue in the repository. |
15 |
| -- Use the **#ideas-and-feedback** channel in our [Discord community](https://discord.gg/QXhHzw7azs) for discussions. |
| 15 | +### 2. Fork and Clone |
16 | 16 |
|
17 |
| -### 2. **Fork and Clone** |
18 |
| -- Fork the repository to your GitHub account. |
19 |
| -- Clone the forked repository to your local machine. |
| 17 | +* Fork this repository to your GitHub account. |
| 18 | +* Clone the forked repository to your local machine: |
20 | 19 |
|
21 | 20 | ```bash
|
22 |
| -git clone https://github.com/YOUR_USERNAME/blok.git |
23 |
| -cd blok |
| 21 | +git clone https://github.com/CharithaReddy18/AI-health-chatbot.git |
| 22 | +cd AI-health-chatbot |
24 | 23 | ```
|
25 | 24 |
|
26 |
| -### 3. **Set Up Your Environment** |
27 |
| -- Follow the instructions in the `README.md` to set up your development environment. |
28 |
| -- Run tests to ensure everything works as expected. |
29 |
| - |
30 |
| -### 4. **Work on Your Contribution** |
31 |
| -- Create a new branch for your work: |
32 |
| - ```bash |
33 |
| - git checkout -b feature/your-feature-name |
34 |
| - ``` |
35 |
| -- Follow the coding style and conventions used in the project. |
36 |
| -- Write clear, concise, and well-documented code. |
37 |
| -- If adding a new feature, include relevant tests. |
38 |
| - |
39 |
| -### 5. **Commit Your Changes** |
40 |
| -- Write meaningful commit messages: |
41 |
| - ```bash |
42 |
| - git commit -m "Add: Feature description" |
43 |
| - ``` |
44 |
| -- Push your changes to your fork: |
45 |
| - ```bash |
46 |
| - git push origin feature/your-feature-name |
47 |
| - ``` |
48 |
| - |
49 |
| -### 6. **Submit a Pull Request** |
50 |
| -- Open a pull request from your branch to the `main` branch of the original repository. |
51 |
| -- Use the pull request template (if available) to provide details about your changes. |
52 |
| -- Ensure that all automated tests pass before submission. |
53 |
| - |
54 |
| ---- |
55 |
| - |
56 |
| -## Code Style and Standards |
57 |
| -- Use ESLint to ensure code consistency. |
58 |
| -- Adhere to the project's architectural patterns and modular design principles. |
59 |
| -- Avoid introducing unnecessary dependencies. |
60 |
| - |
61 |
| ---- |
62 |
| - |
63 |
| -## Reporting Issues |
64 |
| -If you encounter a bug or have a feature request: |
65 |
| -1. Check the Issues to ensure it hasnβt been reported. |
| 25 | +### 3. Set Up Your Environment |
| 26 | + |
| 27 | +* Check the ['README.md'](README.md) for setup instructions. |
| 28 | +* Install requirements based on requirements.txt. |
| 29 | + |
| 30 | +### 4. Work on Your Contribution |
| 31 | + |
| 32 | +* Create a new branch for your work: |
| 33 | + |
| 34 | +```bash |
| 35 | +git checkout -b feature/your-feature-name |
| 36 | +``` |
| 37 | + |
| 38 | +* Follow the coding style and conventions used in the project. |
| 39 | +* Write clear, well-documented code. |
| 40 | +* Add tests if applicable. |
| 41 | + |
| 42 | +### 5. Commit Your Changes |
| 43 | + |
| 44 | +* Use meaningful commit messages: |
| 45 | + |
| 46 | +```bash |
| 47 | +git commit -m "Add: Short description of your change" |
| 48 | +``` |
| 49 | + |
| 50 | +* Push your changes: |
| 51 | + |
| 52 | +```bash |
| 53 | +git push origin feature/your-feature-name |
| 54 | +``` |
| 55 | + |
| 56 | +### 6. Submit a Pull Request |
| 57 | + |
| 58 | +* Open a Pull Request (PR) to the `main` branch of this repository. |
| 59 | +* Fill out the PR template (if available). |
| 60 | +* Make sure all checks/tests pass before requesting review. |
| 61 | + |
| 62 | + |
| 63 | +## π§© Code Style and Standards |
| 64 | + |
| 65 | +* Use ESLint / Prettier (if configured) for consistent formatting. |
| 66 | +* Follow naming conventions and keep code modular. |
| 67 | +* Avoid introducing unnecessary requirements. |
| 68 | + |
| 69 | + |
| 70 | +## π Reporting Issues |
| 71 | + |
| 72 | +If you find a bug or have a feature request: |
| 73 | + |
| 74 | +1. Check the existing issues first. |
66 | 75 | 2. Open a new issue with:
|
67 |
| - - A clear and descriptive title. |
68 |
| - - Steps to reproduce the issue (if applicable). |
69 |
| - - Expected and actual behavior. |
70 | 76 |
|
71 |
| ---- |
| 77 | + * A clear and descriptive title |
| 78 | + * Steps to reproduce (if itβs a bug) |
| 79 | + * Expected vs. actual behavior |
| 80 | + |
| 81 | + |
| 82 | +## π Documentation Contributions |
| 83 | + |
| 84 | +* Update relevant Markdown files (`README.md`, `docs/`) for docs-related changes. |
| 85 | +* Keep writing clear, concise, and beginner-friendly. |
| 86 | + |
| 87 | + |
| 88 | +## π€ Community and Conduct |
| 89 | + |
| 90 | +* Be respectful and collaborative in all interactions. |
| 91 | +* Follow the projectβs [Code of Conduct](CODE_OF_CONDUCT.md). |
| 92 | + |
72 | 93 |
|
73 |
| -## Documentation Contributions |
74 |
| -- For documentation edits, update the relevant markdown files in the `docs/` directory. |
75 |
| -- Follow a clear and concise writing style. |
| 94 | +## β Need Help? |
76 | 95 |
|
77 |
| ---- |
| 96 | +If you have any questions: |
78 | 97 |
|
79 |
| -## Community and Conduct |
80 |
| -- Be respectful and collaborative when interacting with others. |
81 |
| -- Adhere to the project's [Code of Conduct](CODE_OF_CONDUCT.md). |
| 98 | +* Open an issue with the `question` label. |
| 99 | +* Tag project maintainers for clarification. |
82 | 100 |
|
83 |
| ---- |
84 | 101 |
|
85 |
| -## Need Help? |
86 |
| -If you have questions or need help, feel free to: |
87 |
| -- Join our [Discord community](https://discord.gg/QXhHzw7azs). |
88 |
| -- Open an issue with the `question` label. |
| 102 | +Weβre excited to collaborate with you and improve **AI-health-chatbot** together! π‘ |
89 | 103 |
|
90 |
| -Weβre excited to collaborate with you and improve **Blok** together! |
|
0 commit comments