-
Notifications
You must be signed in to change notification settings - Fork 90
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
Fixes licenses issues that were hidden by bug in go-licenses #1718
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
439bb8e
to
210f7c0
Compare
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.
Looks good to me. Happy to lgtm once everyone's had a chance to have a look.
$(FIX_LICENSES_AZURE_TARGET): | $(GO_MOD_DOWNLOAD_TARGETS) | ||
# The azure sdk dependency github repo has a LICENSE however it does not have a go.mod | ||
# checked in to the repo. Hence we need to manually download LICENSE from Github | ||
# and place them in the vendor directory so that they is available for go-licenses to pick up |
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.
nit: "they are" instead of "they is".
/lgtm |
210f7c0
to
551f62c
Compare
/lgtm |
Issue #, if available:
Description of changes:
There was a bug in go-licenses that was incorrectly matching licenses for modules in the vendor directory. Read the specifics in my upstream PR
. Using that PR I have run thru all the projects to confirm what was missed and updated the few spots that needed changes to make sure license files were in the correct locations. There was only a couple and they were similar situations we have seen before.
While getting the upstream PR thru I am going to update our builder-base to use my fork for the time being. This should be able to merge before that is officially rolled out, we just make see a bit of churn on the generated attribution files. I am going to try and time it up tho.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.