> For the complete documentation index, see [llms.txt](https://docs-lunar.earthly.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-lunar.earthly.dev/configuration/lunar-yml.md).

# lunar.yml

Reference for lunar.yml, the optional per-repository file that configures a single component's owner, domain, branch, tags, and CI pipelines.

{% hint style="info" %}
**Coming Soon** — This feature is not yet available.
{% endhint %}

* `lunar.yml`
* Type: YAML file
* Form:

  ```yaml
  version: 0

  owner: <email>
  domain: <domain-path>
  branch: <branch-name>
  tags: [<tag>, <tag>, ...]
  ciPipelines: [<ci-pipeline>, <ci-pipeline>, ...]
  ```

This page describes the configuration of a component via lunar.yml.

The file lunar.yml is optional and it can be used to define the configuration of a single component. If lunar.yml is not provided, the component configuration can be defined in the Lunar configuration file, [lunar-config.yml](/configuration/lunar-config.md). With the exception of the version field, the same fields in `lunar-config.yml -> components.<component-name>` are used in `lunar.yml`.

If a component is defined in both lunar.yml and lunar-config.yml, the settings are merged, and the configuration in lunar-config.yml takes precedence when a scalar field (`owner`, `domain`, `branch`) is defined in both places. The arrays (`tags`, `ciPipelines`) are appended to each other.

## `version`

* `lunar.yml -> version`
* Type: `string`
* Required

The version field is used to specify the version of the component configuration file. The current version is `0`.

## Other Fields

The other fields in `lunar.yml` are the same as those in `lunar-config.yml -> components.<component-name>`. For more information, see the [lunar-config.yml components](/configuration/lunar-config/components.md) page.


---

# 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-lunar.earthly.dev/configuration/lunar-yml.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.