# Contributing to the ProCam2D Plugin

Thank you for your interest in contributing to our plugin! We welcome all contributions, whether it's fixing bugs, adding new features, improving documentation, or other enhancements. Here’s how you can get started:

## How to Contribute

### 1. Open an Issue

Before starting work on a major change, please open an issue to discuss what you would like to change. This helps us coordinate efforts and avoid duplication.

### 2. Fork the Repository

Fork the repository to your own GitHub account by clicking the "Fork" button at the top right of this page. This creates a copy of the repository in your GitHub account.

### 3. Clone Your Fork

Clone your fork to your local machine so you can start working on it.

```sh
git clone https://github.com/daz-b-like/ProCam2D_Godot4.x.git
cd ProCam2D_Godot4.x
```

### 4. Create a Branch

Create a new branch for your changes. It's a good practice to name your branch descriptively.

```sh
git checkout -b feature/new-feature
```

### 5. Make Changes

Make your changes in the new branch. Ensure your changes follow our coding standards and include appropriate documentation.

### 6. Commit Your Changes

Commit your changes with clear and concise commit messages.

```sh
git add .
git commit -m "Add new feature"
```

### 7. Push to Your Fork

Push your changes to your fork on GitHub.

```sh
git push origin feature/new-feature
```

### 8. Open a Pull Request

Go to your forked repository on GitHub and open a pull request. Select the branch you just pushed and provide a clear description of your changes.

### 9. Discuss and Review

We will review your pull request, suggest any necessary changes, and discuss them with you. Once everything looks good, we’ll merge your changes into the main repository.

## Guidelines

- **Open an Issue First**: Before starting work on a major change, please open an issue to discuss what you would like to change. This helps us coordinate efforts and avoid duplication.
- **Coding Standards**: Follow our coding standards and best practices.
- **Write Tests**: If applicable, add tests to ensure your changes are robust.
- **Documentation**: Update the documentation to reflect your changes.
- **Respect**: Be respectful and considerate in your interactions with others.

## Need Help?

If you have any questions or need assistance, feel free to open an issue, and we'll be happy to help.

Thank you for contributing!