Create CONTRIBUTING.md

Author: samialtas

CONTRIBUTING.md

@@ -0,0 +1,88 @@
+# Contributing to the Excel-Style Color Picker for WinForms 🎨
+
+🎉 First off, thank you for considering contributing! We're thrilled you're here and interested in making this project even better. Your contributions are what make the open-source community such an amazing place.
+
+This document provides a set of guidelines for contributing to this project. These are mostly guidelines, not strict rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
+
+## 🤝 Code of Conduct
+
+This project and everyone participating in it is governed by our [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior.
+
+## 🤔 How Can I Contribute?
+
+There are many ways to contribute, and not all of them involve writing code. We value all forms of contribution!
+
+- **🐛 Reporting Bugs**: If you find a bug, please let us know!
+- **💡 Suggesting Enhancements**: Have a great idea for a new feature or an improvement to an existing one? We'd love to hear it.
+- **👨‍💻 Writing Code**: Help fix bugs or add new features by submitting a pull request.
+- **📖 Improving Documentation**: If you see a typo, a confusing sentence, or a section that could be clearer in our `README.md` or other documentation, feel free to submit a fix.
+
+### 🐛 Reporting Bugs
+
+Before creating a bug report, please **check the existing issues** to see if someone has already reported the problem.
+
+When you create a bug report, please include as many details as possible:
+
+1. **A clear and descriptive title** for the issue.
+2. **Steps to reproduce the bug**. A minimal, reproducible example is a huge help!
+3. **What you expected to happen** versus **what actually happened**.
+4. **Screenshots or GIFs** are incredibly helpful for UI-related bugs.
+5. **Your environment details**, such as your .NET version and Windows version.
+
+### 💡 Suggesting Enhancements
+
+We're always looking for ideas to improve this component. To suggest an enhancement:
+
+1. **Start by creating a new issue**.
+2. **Provide a clear and descriptive title**.
+3. **Explain your idea in detail**. Why would this be a useful addition? What problem does it solve?
+4. **Include sketches, mockups, or examples** if possible.
+
+## 👨‍💻 Your First Code Contribution (Pull Requests)
+
+Ready to write some code? Great! Here’s how to set up for a pull request.
+
+### Development Setup
+
+1. **Fork** the repository on GitHub.
+2. **Clone** your fork to your local machine:
+ ```bash
+ git clone https://github.com/samialtas/CSharpColorPicker.git
+ ```
+3. **Open the project** in Visual Studio.
+4. **Create a new branch** for your changes. Please use a descriptive branch name:
+ ```bash
+ git checkout -b feature/new-feature
+ # or
+ git checkout -b fix/bug-that-i-fixed
+ ```
+
+### Pull Request Process
+
+1. **Make your changes** in your new branch. Please follow the style guide below.
+2. **Ensure the project builds** without any errors.
+3. **Test your changes** to make sure they work as expected and don't introduce new bugs.
+4. **Update the `README.md`** or other documentation if your changes affect it (e.g., adding a new property or feature).
+5. **Commit your changes** with a clear and concise commit message.
+ ```bash
+ git commit -m "feat: Add a new property to the control"
+ ```
+6. **Push your branch** to your fork on GitHub:
+ ```bash
+ git push origin feature/my-new-feature
+ ```
+7. **Open a Pull Request** (PR) from your fork's branch to the `main` branch of the original repository.
+8. **Fill out the PR template**. Provide a clear title and a detailed description of your changes. If your PR fixes an existing issue, be sure to link it using keywords like `Closes #123`.
+
+### 🎨 Style Guide
+
+To keep the codebase consistent and easy to read, please follow these guidelines:
+
+- **Match the existing coding style.** Look at the existing code to get a feel for the patterns used.
+- Follow standard C#/.NET naming conventions (e.g., `PascalCase` for methods, properties, and classes; `camelCase` for local variables).
+- Add comments to explain complex or non-obvious parts of your code.
+- Use meaningful names for variables, methods, and classes.
+
+---
+
+Thank you again for your interest in contributing. We can't wait to see what you create! ✨