Start generating .gitattributes
file for generated and vendored RBI files
#1604
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Fixes https://github.com/Shopify/ruby-dev-exp-issues/issues/651
The
linguist
gem added support for detecting generated and vendored RBI files in github-linguist/linguist#6143, but it parses the RBI file header comments to understand that, which is quite brittle.Tapioca can do a better job of this, since it already knows that
dsl
andgem
commands will create "generated" RBI files in the output directory and theannotations
command will create "vendored" RBI files. So, Tapioca should be generating the appropriate.gitattributes
files in the relevant output directories to signal that the RBI files contained are generated/vendored.Implementation
GitAttributes
helper module that knows how to create.gitattributes
files that state the**/*.rbi
files in the folder are either generated or vendored RBI files.DslGenerate
,GemGenerate
,GemSync
andAnnotations
commands to create appropriate.gitattributes
files in the output folder.Tests
Added extra test cases for checking generated
.gitattributes
files.