You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+29-4Lines changed: 29 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -180,13 +180,25 @@ Ruby:
180
180
…
181
181
```
182
182
183
-
If a file's language was overridden using `.gitattributes`, the strategy will show the original detection method along with an override note (fictional example):
183
+
If a file's language is affected by `.gitattributes`, the strategy will show the original detection method along with a note indicating whether the gitattributes setting changed the result or confirmed it.
184
+
185
+
For instance, if you had the following .gitattributes overrides in your repo:
186
+
187
+
```gitattributes
188
+
189
+
*.ts linguist-language=JavaScript
190
+
*.js linguist-language=JavaScript
191
+
192
+
```
193
+
194
+
the output of Linguist would be something like this:
184
195
185
196
```console
186
197
100.00% 217 JavaScript
187
198
188
199
JavaScript:
189
200
demo.ts [Heuristics (overridden by .gitattributes)]
If a file's language was overridden using`.gitattributes`, the strategy will show the original detection method along with an override note:
256
+
If a file's language is affected by`.gitattributes`, the strategy will show whether the gitattributes setting changed the result or confirmed it:
245
257
258
+
In this ficticious example, it says "confirmed by .gitattributes" since the detection process (using the Filename strategy) would have given the same output as the override:
0 commit comments