> For the complete documentation index, see [llms.txt](https://docs.lawnchair.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lawnchair.app/developers/standards/development-workflow.md).

# Development workflow

The review process scales with a change's complexity and risk. Unless noted otherwise, pull requests (PRs) must target the `16-dev` branch.

### Change tiers

The complexity and risk of a change determine the review protocol.

<table><thead><tr><th width="95">Tier</th><th>Definition</th><th>Examples</th><th>Protocol</th></tr></thead><tbody><tr><td><strong>Trivial</strong></td><td>Zero risk of regression.</td><td>Typos, documentation, style fixes.</td><td>Commit directly to the active branch.</td></tr><tr><td><strong>Simple</strong></td><td>Functionally isolated changes with low risk.</td><td>Single-file bug fixes, minor UI polish.</td><td>Create PR, assign reviewer, enable auto-merge.</td></tr><tr><td><strong>Medium</strong></td><td>Changes affecting multiple components.</td><td>New settings screens, drawer search providers.</td><td>Detailed PR, requires core team review.</td></tr><tr><td><strong>Major</strong></td><td>High-risk, core architectural changes.</td><td>Android version rebases, subsystem rewrites.</td><td>Detailed PR, mandatory formal approval required.</td></tr></tbody></table>

### Commit conventions

We follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification. Commits should use the following format: `type(scope): subject`.

Allowed types include: `feat`, `fix`, `style`, `refactor`, `perf`, `docs`, `test`, and `chore`.

### Versioning scheme

Lawnchair version codes utilize a five-part structure to ensure compatibility and track development stages.

1. **Android major version**
2. **Android minor version**
3. **Development stage** (00: Dev, 01: Alpha, 02: Beta, 03: RC, 04: Release)
4. **Development version**
5. **Revision number**

The following table lists the development stages used by Lawnchair:

<table><thead><tr><th width="166">Stage</th><th width="126">Denoted by</th></tr></thead><tbody><tr><td>Development</td><td>00</td></tr><tr><td>Alpha</td><td>01</td></tr><tr><td>Beta</td><td>02</td></tr><tr><td>Release Candidate</td><td>03</td></tr><tr><td>Release</td><td>04</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lawnchair.app/developers/standards/development-workflow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.