-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
common: assume vendored resources are binary #3124
Conversation
Previously Dependabot included a list of binary mime types and encoded only binary files. Invert to include a list of acceptable text mime types to leave un-encoded. Per the included test, the edge case here is `iso-8859-1` strings, which aren't binary but also aren't valid `utf-8`.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one! I actually thought we'd already done this at some point 😄
Thank you @thepwagner for this fix. Any estimate on when this will be deployed? |
@filipkis sorry for the delay, this slipped over a long weekend here! This is now live, as of: |
No worries, not a big delay :) I run the dependabot on the test repo and while PRs do get create they have many files (instead of just one or couple of gems). It seems that gems somehow get unpacked. Here is an example |
@filipkis isn't that expected? Since json_vat uses a git dependency, "vendoring" means copying that repository's contents at the target commit.
Treating vendored git dependencies differently than vendored gems is a separate concern. Dependabot assumes all dependencies are fully vendored, or none are. |
Well, maybe :) In our workflow I was before relying on only things that were added to So yes, I guess this is correct behaviour. And we'll just need to do the initial commit of these (or maybe add them to Btw. is there any chance down the road this will be configurable (to exclude git dependancies)? |
Previously Dependabot included a list of binary mime types and encoded
only binary files.
Invert to include a list of acceptable text mime types to leave
un-encoded.
Per the included test, the edge case here is
iso-8859-1
strings, whicharen't binary but also aren't valid
utf-8
.Related