| Severity | Warning |
| Reported by | Metalama.Framework |
| Message | A Metalama repository configuration file (metalama.json) has been ignored. <Reason> |
Cause
A metalama.json file at the root of a git repository configures Metalama for the whole repository. Currently, its only setting lets you opt out of telemetry, as described in Telemetry. Metalama looks for the repository root, which is the nearest parent directory that contains a .git folder or file, and reads metalama.json there.
Metalama reports LAMA0075 when it ignores a metalama.json file. The text that replaces <Reason> gives the path of the file and the reason:
- The file is located in a subdirectory of the repository, for instance in a project directory, instead of the repository root. Metalama only reads the file at the root.
- The file at the repository root can't be read, for instance because of missing permissions.
- The file at the repository root isn't valid JSON or doesn't match the expected schema.
The warning points to the ignored metalama.json file. An ignored file has no effect: if it opts out of telemetry, the opt-out doesn't apply. The metalama telemetry status command shows the same warnings.
This diagnostic depends on files of the repository outside of the project, so it can't be shown in an example.
Resolution
If the file is misplaced, move it to the repository root, that is, the directory that contains the
.gitfolder, and merge its settings with anymetalama.jsonfile that's already there.If the file can't be read, check its permissions and whether another process locks it.
If the file is malformed, correct its content. For instance, the following file disables telemetry for the repository:
{ "telemetry": { "enabled": false } }If you don't need the file, delete it.
Then run metalama telemetry status from the repository directory to check that no warning remains.