<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=572763) </details> <!--IssueSummary end--> ## Problem We are experiencing weird issues when using gitlab-generated attribute in .gitattributes. This is best illustrated by Gitlab's own repository: https://gitlab.com/gitlab-com/runbooks/-/merge_requests/9492/diffs You can see how some of "autogenerated" files are marked as generated, and some are not (in the screenshot, I collapsed it by hand, but you can see how the automatic note about generated file is missing). {width=924 height=646} That repo only has one rule: ``` **/autogenerated-*.yml gitlab-generated ``` We experience similar issue on a bigger scale (private repo on gitlab.com) - some folders are ignored , sometimes individual files, and it's hard to tell what's the pattern of this behavior. We're pretty sure it's not a configuration issue on our end as testing `git check-attr` returns 'gitlab-generated: set' for files that Gitlab fails to mark. ## Proposal TBD, needs investigation.