rules_webtesting
rules_webtesting copied to clipboard
bazelbuild
Kotlin Support / Scala Fix
See enclosed commits - fixes an issue with Scala dependencies, and introduces Kotlin support via the same route as Scala.
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.
ℹ️ Googlers: Go here for more info.
![google-cla[bot] avatar](https://avatars.githubusercontent.com/in/42202?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi Sam, it looks like you haven't signed our CLA yet. We can't accept this contribution until you've signed it; please visit https://cla.developers.google.com/clas to address this. Thanks!
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.
ℹ️ Googlers: Go here for more info.
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.
ℹ️ Googlers: Go here for more info.
Sorry for the difficulties, Sam. Here's what's going on:
- You've signed a corp CLA using your publicly listed [email protected] email address.
- Commits in this PR are associated with email addresses [email protected], [email protected], and [email protected], none of which have signed a CLA.
Since you happen to be the CLA administrator for your corp CLA, you can add your alternate email addresses to the CLA group you manage. Alternatively, you can re-push the commits with the known email address (help).
Sorry, I'm no longer actively working on this project. Please re-assign this back to @mtrea .
Somehow I can't re-assign it by myself.
