> ## Documentation Index
> Fetch the complete documentation index at: https://docs.twenty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bugs, Requests & Pull Requests

## Reporting Bugs

To report a bug, please [create an issue on GitHub](https://github.com/twentyhq/twenty/issues/new).

You can also ask for help on [Discord](https://discord.gg/cx5n4Jzs57).

## Feature Requests

If you're not sure if it's a bug, and you feel it's closer to a feature request, then you should probably [open a discussion instead](https://github.com/twentyhq/twenty/discussions/new).

## Submit a Pull Request

Contributing code to Twenty starts with a pull request (PR).

### Before You Start

1. Check [existing issues](https://github.com/twentyhq/twenty/issues) for related work
2. For new features, open an issue first to discuss
3. Review our [Code of Conduct](https://github.com/twentyhq/twenty/blob/main/CODE_OF_CONDUCT.md)

### Fork and Clone

1. Fork the repository on GitHub
2. Clone your fork:

```bash theme={null}
git clone https://github.com/YOUR_USERNAME/twenty.git
cd twenty
```

3. Add upstream remote:

```bash theme={null}
git remote add upstream https://github.com/twentyhq/twenty.git
```

### Create a Branch

```bash theme={null}
git checkout -b feature/your-feature-name
```

Use descriptive branch names:

* `feature/add-export-button`
* `fix/login-redirect-issue`
* `docs/update-api-guide`

### Make Your Changes

1. Write clean, well-documented code
2. Follow existing code style
3. Add tests for new functionality
4. Update documentation if needed

### Submit Your PR

1. Push your branch:

```bash theme={null}
git push origin feature/your-feature-name
```

2. Open a PR on GitHub
3. Fill in the PR template
4. Link related issues

### PR Checklist

* [ ] Code follows project style guidelines
* [ ] Tests pass locally
* [ ] Documentation is updated
* [ ] PR description explains the changes