Follow .gitattributes export-ignore semantics

[vshymanskyy]

Arduino libraries are stored on github, and can define export-ignore in .gitattributes file to specify what exactly needs to go into a release Zip file.
For example, when I click on "Source Code link" on the latest TinyGSM library (https://github.com/vshymanskyy/TinyGSM/releases/latest ), the Zip file I get does not contain the extras folder at all.

I think Arduino Library Manager should follow these semantics when it grabs the library from github.

Additional context

Additional requests

• Follow .gitattributes export-ignore semantics #59 (comment)

[HomeSpan]

@per1234, thanks for linking this to the original issue, though it looks like it's been open for a while. I'm not sure why this had not surfaced before. The Arduino Library manager must be pulling code in a custom fashion (or perhaps it is cloning the entire repo and then building each release separately?) because simply accessing the releases on GitHub yields the correct response. There is no need to follow the semantics of export-ignore or even know about .gitattributes. The archived release files already incorporate that logic when a new tag/release is created.