> For the complete documentation index, see [llms.txt](https://engineering.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engineering.umh.app/engineering/product-engineer/code-owner.md).

# Code Owner

Who reviews and keeps a part of the codebase in shape, and who the Code Owners are today.

**As a Code Owner, you make sure the code in your part of the codebase is high quality, maintainable and easy to extend.** That includes everything around the code, such as CI/CD, GitHub Actions, linters and coding conventions. To keep it that way, you review every pull request in your part and [decide whether it can be merged](/engineering/development-process/how-to-build/code-review.md#what-the-code-owner-checks). On a [rollout ticket](/engineering/development-process/how-to-decide-what-to-build.md#rollout-tickets), you confirm the implementation is sound and aligns with the codebase. You also make sure your part has the tests that let changes be reviewed and merged quickly. You need to know the language and the best practices of that part of the software.

**When fixing a piece of tech debt in your part needs an engineering decision, you pick the way**, as [Tech debt](/engineering/development-process/how-to-build/tickets/tech-debt.md#obvious-tech-debt-and-decisions) describes.

**Most of the code has no Code Owner yet.** Most of it was written before we had Code Owners. UMH has existed for a long time. Over the past one to two years we have continuously raised our engineering practices. Code ownership is one place where we are still catching up.

**Until someone takes over a part, the CTO is its Code Owner by default.** The `CODEOWNERS` file names the CTO and a second approver for when the CTO is away. Today it only sets who approves the release pull request into `main`. It is not a list of Code Owners yet.

Once a repository releases from its `staging` branch, its `CODEOWNERS` file will list the Code Owner of every part. Until then, ask the CTO who the Code Owner of a part is.


---

# 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://engineering.umh.app/engineering/product-engineer/code-owner.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.