-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with language stats bar #1
Comments
Let Github know that .bas, .cls and .frm extensions stand for Visual Basic for Applications in this repository. Thanks to DecimalTurn for the suggestsion, see #1
Thanks for the recommendation - I didn't know about linguist-language in .gitattributes. Your suggestion is implemented with cbb7c22 |
My pleasure! I'll let you decide if you want to do the same for you other VBA repos such as: Also, I see that some .vb file might contain VBA code, am I mistaken? |
Thanks again - I postboned doing this for way too long and have finally done it today! |
No worries, thanks for providing theses ressources. Just curious what is the name of the editor in question? Also, my list was not exhaustive it seems. There are still a few repos with the same issue:
|
Oh... there were some repos I successfully managed to forget about - thanks anyway for your effort, much appreciated. |
Currently, the GitHub stats bar for this repo doesn't even include VBA:
This is partially because none of the files contain any of the normal metadata that appears at the top of VBA files when they are exported via the VBE. For example, when a module is exported to a .bas file with the VBE, it will include the following metadata at the top of the file:
One way to fix this issue would be to add this metadata manually or via a script, but if you don't want to bother with that and just fix the stats bar, you could add a
.gitattributes
file with the following lines to your repo:This will serve to override those files extensions to make sure they are counter as VBA in the stats bar. Let me know if you'd prefer me to make a PR for that.
The text was updated successfully, but these errors were encountered: