Skip to content

fix: rename .gitattribute to .gitattributes so git actually reads it#2656

Open
devteamaegis wants to merge 1 commit into
modelcontextprotocol:mainfrom
devteamaegis:fix-gitattributes-filename
Open

fix: rename .gitattribute to .gitattributes so git actually reads it#2656
devteamaegis wants to merge 1 commit into
modelcontextprotocol:mainfrom
devteamaegis:fix-gitattributes-filename

Conversation

@devteamaegis
Copy link
Copy Markdown

Summary

The repo root contains a file named `.gitattribute` (singular). Git only reads `.gitattributes` (plural) — so the existing file is a silent no-op.

The file's contents:

```

Generated

uv.lock linguist-generated=true
```

…clearly intend to flag `uv.lock` as generated for GitHub Linguist, but that intent is not currently in effect.

Reproduction

```console
$ git check-attr linguist-generated uv.lock
uv.lock: linguist-generated: unspecified
```

After renaming to `.gitattributes`:

```console
$ git check-attr linguist-generated uv.lock
uv.lock: linguist-generated: true
```

Change

A single `git mv .gitattribute .gitattributes` — no content changes.

Novelty

`gh search prs/issues --repo modelcontextprotocol/python-sdk gitattribute` returned no existing PR or issue about this. The misspelled name was introduced in #1459 and has remained since.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant