Skip to content

Let's use AI to Earn!

Create CONTRIBUTING.md

yika4ba0c8102ffe
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 00000000..e40fdf2f
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,57 @@
+# Contribution Guide
+
+Thank you for your interest in the AiToEarn project! We welcome all forms of contributions, including but not limited to bug reports, feature requests, code improvements, and documentation enhancements.
+
+## Table of Contents
+
+- [Contribution Guide](#contribution-guide)
+ - [Table of Contents](#table-of-contents)
+ - [Code of Conduct](#code-of-conduct)
+ - [Development Environment Setup](#development-environment-setup)
+ - [Submitting Pull Requests](#submitting-pull-requests)
+ - [Reporting Bugs](#reporting-bugs)
+ - [Suggesting New Features](#suggesting-new-features)
+ - [Code Review](#code-review)
+
+## Code of Conduct
+
+Please follow our code of conduct to ensure all participants can communicate in an open and friendly environment.
+
+## Development Environment Setup
+
+1. Fork the project to your own GitHub account
+2. Create a feature branch:
+ ```bash
+ git checkout -b feature/your-feature-name
+ ```
+3. Commit your changes:
+ ```bash
+ git add .
+ git commit -m "feat: add new feature"
+ ```
+4. Push to your forked repository:
+ ```bash
+ git push origin feature/your-feature-name
+ ```
+5. Create a Pull Request on GitHub
+
+## Reporting Bugs
+1. Ensure the bug has not been reported in other issues
+2. Create a new issue and include the following information:
+ - Title describing the bug
+ - Detailed description of the bug
+ - Steps to reproduce the bug
+ - Screenshots (if available)
+ - Other information (such as error logs, stack traces, etc.)
+## Suggesting New Features
+1. Ensure the feature has not been requested in other issues
+2. Create a new issue and include the following information:
+ - Title describing the new feature
+ - Detailed description of the new feature
+ - Screenshots (if available)
+## Code Review
+1. Create a pull request
+2. Wait for other contributors to review the code
+3. Modify the code and commit the new changes
+4. Push the new commits to your forked repository
+5. Ensure the pull request is merged into the main repository