---
title: Pull Request Guide | Contributing to Capawesome
description: How to submit pull requests to Capawesome — assign an issue, branch, commit, follow code standards, and test your changes.
---

# Pull Requests

We welcome pull requests! Following these steps helps us review and merge your changes quickly.

## Before you start

### Assign an issue

Every pull request should be associated with an open issue. If there isn't one yet, create it first. Make sure the issue is **assigned to you** before you start working — this lets us flag any special requirements (such as type definitions) up front and avoids duplicate work.

## Making changes

### Branch

Create a feature branch off the default branch for your change rather than committing to it directly.

### Commit messages

Write clear, descriptive commit messages. We use [Conventional Commits](https://www.conventionalcommits.org/){:target="_blank"} (e.g. `fix:`, `feat:`, `docs:`) — match the style of the repository's history.

### Code style

Follow the existing code style and conventions of the repository. Most repositories include linting and formatting configuration — run them before committing, and make sure your change reads like the surrounding code.

### Tests

Add or update tests for your change where the repository has a test suite, and make sure the existing tests pass.

## Opening the pull request

- Reference the related issue in the description (e.g. `Closes #123`).
- Describe what changed and why, and how you verified it.
- Keep the PR focused — smaller, single-purpose PRs are easier to review.

Once opened, a maintainer will review your changes and may request adjustments before merging. Thank you for contributing!