# Integration owner

> A person or team responsible for an integration, listed in its manifest, who gets notified about its issues and asked to review its pull requests.

Source: https://contributors.home-assistant.io/glossary/integration-owner/

- In code: `codeowners (manifest)`, `CODEOWNERS`
- Also: integration owners
- Formerly: code owner (old name: don't use it in new text)

Integration owners are listed with their GitHub handles in the `codeowners` field of the manifest of an integration. Hassfest generates the `CODEOWNERS` file of Home Assistant Core from those lists, which GitHub uses to ask them for reviews. When an issue gets the label of their integration, the bot mentions them.

The code calls them code owners: the `codeowners` field, the `CODEOWNERS` file, and labels like `by-code-owner`. In text about integrations, say integration owner. "Code owner" still fits a `CODEOWNERS` file of a repository that is not about integrations, like the teams that own parts of the frontend.

## Related terms

- [Integration](https://contributors.home-assistant.io/glossary/integration/): A package of code that connects Home Assistant to a device, service, or protocol, or adds a feature like automations.
- [Manifest](https://contributors.home-assistant.io/glossary/manifest/): The `manifest.json` file of an integration: its domain, name, integration owners, requirements, and how it can be discovered.
- [Pull request](https://contributors.home-assistant.io/glossary/pull-request/): A request on GitHub to merge a change into a repository, where it is reviewed before it goes in.
- [Maintainer](https://contributors.home-assistant.io/glossary/maintainer/): A contributor who can approve and merge pull requests in a repository.