Skip to content

Commit 9113c3a

Browse files
committed
added contributing.md
1 parent a71607b commit 9113c3a

File tree

1 file changed

+97
-0
lines changed

1 file changed

+97
-0
lines changed

CONTRIBUTING.md

Lines changed: 97 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,97 @@
1+
# Contributing to Smart Learning API
2+
3+
Thank you for your interest in contributing to the TaskFlow API repository. We appreciate your support in making this project better. Before you get started, please take a moment to review the guidelines below to ensure a smooth and effective contribution process.
4+
5+
## Introduction
6+
7+
TaskFlow API is a Task Management Application RESTful API. The objectives of this application is to provide users with tools and features that help them efficiently manage their tasks, improve productivity, and stay organized.
8+
9+
## Getting Started
10+
11+
To set up the development environment and run the API locally, please follow the steps outlined in the [README.md](README.md) file. It contains detailed instructions on cloning the repository, creating a virtual environment, installing dependencies, and starting the development server.
12+
13+
## Contributing Process
14+
15+
To contribute to the TaskFlow API repository, please follow these steps:
16+
17+
1. Fork the repository on GitHub:
18+
- Click the "Fork" button in the top-right corner of the repository page.
19+
20+
2. Clone your forked repository to your local machine:
21+
- Use the following command to clone the repository:
22+
```
23+
git clone <your_forked_repository_url>
24+
```
25+
26+
3. Create a new branch for your feature or bug fix:
27+
- Use a descriptive name for your branch. For example:
28+
```
29+
git checkout -b feature/your-feature
30+
```
31+
or
32+
```
33+
git checkout -b bugfix/your-bugfix
34+
```
35+
36+
4. Make the necessary changes and stage them for commit:
37+
- Use the following command to stage your changes:
38+
```
39+
git add .
40+
```
41+
42+
5. Commit the changes with a clear and concise commit message:
43+
- Use the following command to commit your changes:
44+
```
45+
git commit -m 'Add some feature'
46+
```
47+
48+
6. Push the changes to your forked repository:
49+
- Use the following command to push your changes:
50+
```
51+
git push origin feature/your-feature
52+
```
53+
54+
7. Navigate to the original repository on GitHub and create a pull request:
55+
- Click the "Compare & pull request" button next to your pushed branch.
56+
57+
8. Provide a clear and descriptive title and description for your pull request, explaining the purpose and changes made.
58+
59+
9. Be responsive to any feedback or changes requested during the review process:
60+
- Iterate on your changes if necessary and update the pull request accordingly.
61+
62+
## Coding Guidelines
63+
64+
When contributing to the TaskFlow API, please adhere to the following coding guidelines:
65+
66+
- Use consistent indentation with 4 spaces and follow the PEP 8 style guide for Python code.
67+
- Write clear and meaningful variable and function names that accurately describe their purpose.
68+
- Include comments where necessary to improve code readability and provide explanations for complex logic.
69+
- Follow best practices and apply common software engineering principles to ensure high-quality code.
70+
71+
## Testing
72+
73+
Writing tests is highly encouraged for any new features or bug fixes to ensure the stability and reliability of the API. Please follow the guidelines below:
74+
75+
- Write clear and comprehensive tests that cover the functionality being implemented or fixed.
76+
- Run the tests locally to ensure they pass successfully before submitting your pull request.
77+
- Aim for a test coverage of at least 80% to ensure adequate test protection.
78+
79+
## Documentation
80+
81+
Maintaining clear and comprehensive documentation is essential for the TaskFlow API. Please consider the following:
82+
83+
- Update the [README.md](README.md) file to reflect any changes or additions made to the project. Provide clear and concise explanations of the API endpoints, their purpose, and how to use them.
84+
- Include docstrings in your code to provide inline documentation and improve code comprehension. Follow the standard conventions for docstring formatting.
85+
86+
## Issue and Discussion
87+
88+
If you encounter a bug, have a question, or want to suggest an improvement, please create a new issue in the repository. We value your feedback and participation in discussions related to the TaskFlow API.
89+
90+
When creating an issue, be sure to provide a clear and detailed description of the problem or suggestion. If applicable, include steps to reproduce the issue and any relevant error messages or logs.
91+
92+
## License
93+
94+
By contributing to the TaskFlow API repository, you agree that your contributions will be licensed under the [MIT License](LICENSE). This ensures that your contributions can be freely used, modified, and distributed by others.
95+
96+
If you have any further questions or need additional assistance, please don't hesitate to reach out. We appreciate your contribution and look forward to your involvement in making the TaskFlow API even better!
97+

0 commit comments

Comments
 (0)