Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Mark generated files as linguist-generated

Open Beginner friendly
  • Is something wrong?
#203 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #205 by @ump45nose — closed without merging

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
git, github, swift
Domain
tooling

Research direction

Add the three patterns from the issue to a .gitattributes file at the repository root, each with linguist-generated=true. Read the existing repository attributes first, if present, and confirm the patterns match the generated Swift files named in the issue. Done when GitHub Linguist treats those files as generated.

Written by the indexing model from the issue text.

Description

Describe the enhancement requested

We commit generated source files to this repository:

  • FlatBuffers: Sources/Arrow/*_generated.swift
  • Protocol Buffers/gRPC: Sources/ArrowFlight/*.pb.swift and Sources/ArrowFlight/*.grpc.swift

When these files are regenerated, for example on a FlatBuffers or gRPC Swift upgrade such as #201 and #202, their changes dominate the PR diff. This makes the hand-written changes harder to review.

GitHub doesn't detect these files as generated automatically because they start with the ASF license header.

How about adding a .gitattributes that marks them as linguist-generated? GitHub collapses diffs of such files in PRs by default, and they can still be expanded when needed:

Sources/Arrow/*_generated.swift linguist-generated=true
Sources/ArrowFlight/*.pb.swift linguist-generated=true
Sources/ArrowFlight/*.grpc.swift linguist-generated=true

See also: https://docs.github.com/en/repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github

Dominant language
Swift
Stars
33
Forks
18
Avg merge
1h 38m
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/arrow-swift

All issues in apache/arrow-swift

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.