|
@@ -14,14 +14,11 @@ Bug reports help make Cline better for everyone! Before creating a new issue, pl
|
|
|
## Before Contributing
|
|
## Before Contributing
|
|
|
|
|
|
|
|
All contributions must begin with a GitHub Issue, unless the change is for small bug fixes, typo corrections, minor wording improvements, or simple type fixes that don't change functionality.
|
|
All contributions must begin with a GitHub Issue, unless the change is for small bug fixes, typo corrections, minor wording improvements, or simple type fixes that don't change functionality.
|
|
|
-
|
|
|
|
|
-- **Check existing issues**: Search [GitHub Issues](https://github.com/cline/cline/issues).
|
|
|
|
|
-- **Create an issue**: Use appropriate templates:
|
|
|
|
|
- - **Contributions:** Use the "Contribution Request" template to propose what you'd like to work on.
|
|
|
|
|
- - **Bugs:** "Bug Report" template for reporting issues.
|
|
|
|
|
- - **Features:** "Detailed Feature Proposal" template for suggesting new features.
|
|
|
|
|
-- **Wait for approval**: A core Cline contributor must approve your contribution request before you start implementation.
|
|
|
|
|
-- **Claim issues**: Once approved, the issue will be assigned to you.
|
|
|
|
|
|
|
+**For features and contributions**:
|
|
|
|
|
+- First check the [Feature Requests discussions board](https://github.com/cline/cline/discussions/categories/feature-requests) for similar ideas
|
|
|
|
|
+- If your idea is new, create a new feature request
|
|
|
|
|
+- Wait for approval from core maintainers before starting implementation
|
|
|
|
|
+- Once approved, feel free to begin working on a PR with the help of our community!
|
|
|
|
|
|
|
|
**PRs without approved issues may be closed.**
|
|
**PRs without approved issues may be closed.**
|
|
|
|
|
|