linguist-generated in .gitattributes files are not handled properly #2017

lacus_oblivionis commented 2025年07月09日 13:33:45 +02:00

Comment

I'm using Pixi, a Cargo-like package management tool for Conda/Python Ecosystem which generates YAML Lock File (pixi.lock), in my private project.

Pixi will generate a .gitattributes file when initializing a project:

# SCM syntax highlighting & preventing 3-way merges
pixi.lock merge=binary linguist-language=YAML linguist-generated=true

linguist-generated=true means that pixi.lock is auto-generated and should be hidden from language statistics.

However, when I updated my code to Codeberg, the pixi.lock file was still included in the language statistics.

It seems that this issue have been solved/closed in Forgejo (#7677 in forgejo/forgejo), but still can be reproduced in Codeberg.

### Comment I'm using [Pixi](https://pixi.sh/latest/), a Cargo-like package management tool for Conda/Python Ecosystem which generates [YAML Lock File (`pixi.lock`)](https://pixi.sh/latest/workspace/lockfile/), in my private project. Pixi will generate a `.gitattributes` file when initializing a project: ``` # SCM syntax highlighting & preventing 3-way merges pixi.lock merge=binary linguist-language=YAML linguist-generated=true ``` `linguist-generated=true` means that `pixi.lock` is auto-generated and should be hidden from language statistics. However, when I updated my code to Codeberg, the `pixi.lock` file was still included in the language statistics. It seems that this issue have been solved/closed in Forgejo ([#7677 in forgejo/forgejo](https://codeberg.org/forgejo/forgejo/issues/7677)), but still can be reproduced in Codeberg.

Gusted commented 2025年07月09日 14:48:44 +02:00

Please link the repository where you are seeing this behavior.

Please link the repository where you are seeing this behavior.

lacus_oblivionis commented 2025年07月09日 15:25:39 +02:00

@Gusted wrote in #2017 (comment):

Please link the repository where you are seeing this behavior.

Here is an MWE that can reproduce this behavior: (削除) https://codeberg.org/hikat/pixi-sample (削除ここまで)

mkdir pixi-sample
cd pixi-sample
pixi init
echo "print(\"Hello World\")" >> main.py

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/2017#issuecomment-5767469: > Please link the repository where you are seeing this behavior. Here is an MWE that can reproduce this behavior: ~~https://codeberg.org/hikat/pixi-sample~~ ```sh mkdir pixi-sample cd pixi-sample pixi init echo "print(\"Hello World\")" >> main.py ```

Gusted commented 2025年07月09日 17:24:55 +02:00

Is there a reason why you want syntax highlighting for a generated file? It's a easy fix none-the-less but specifying both linguist-language and linguist-generated is what is causing the issue and I do not think anyone imagined these options to be used together.

Is there a reason why you want syntax highlighting for a generated file? It's a easy fix none-the-less but specifying both `linguist-language` and `linguist-generated` is what is causing the issue and I do not think anyone imagined these options to be used together.

lacus_oblivionis commented 2025年07月09日 17:57:05 +02:00

@Gusted wrote in #2017 (comment):

Is there a reason why you want syntax highlighting for a generated file?

No. This .gitattributes file is auto-generated by pixi init.

The following content is from Pixi's doc (https://pixi.sh/v0.49.0/first_project/#creating-a-pixi-project):

To create a new Pixi project, you can use the pixi init command:

pixi init my_project

This command creates a new directory called my_project with the following structure:

my_project
├── .gitattributes
├── .gitignore
└── pixi.toml

---

@Gusted wrote in #2017 (comment):

It's a easy fix none-the-less but specifying both linguist-language and linguist-generated is what is causing the issue and I do not think anyone imagined these options to be used together.

It works:

# SCM syntax highlighting & preventing 3-way merges
# pixi.lock merge=binary linguist-language=YAML linguist-generated=true
pixi.lock merge=binary linguist-generated=true

Maybe I should report this issue to Pixi community.

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/2017#issuecomment-5769038: > Is there a reason why you want syntax highlighting for a generated file? No. This `.gitattributes` file is auto-generated by `pixi init`. The following content is from Pixi's doc (https://pixi.sh/v0.49.0/first_project/#creating-a-pixi-project): > To create a new Pixi project, you can use the pixi init command: > ```sh > pixi init my_project > ``` > > This command creates a new directory called my_project with the following structure: > ``` > my_project > ├── .gitattributes > ├── .gitignore > └── pixi.toml > ``` --- @Gusted wrote in https://codeberg.org/Codeberg/Community/issues/2017#issuecomment-5769038: > It's a easy fix none-the-less but specifying both `linguist-language` and `linguist-generated` is what is causing the issue and I do not think anyone imagined these options to be used together. It works: ``` # SCM syntax highlighting & preventing 3-way merges # pixi.lock merge=binary linguist-language=YAML linguist-generated=true pixi.lock merge=binary linguist-generated=true ``` Maybe I should report this issue to Pixi community.