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 have the pull request author add another comment and the bot will run again. If the bot doesn't comment, it means it doesn't think anything has changed.

CLAs look good, thanks!

Happy New Year to you too! 🎉🎉🎉

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

caretaker: no g3 impact

Oh George, I'm really disappointed that you didn't notice that there is one more:

dang! You found that one as well! How can you be this awesome?!? You are incredible! 🙇

I tried to decrease the number of copyright notices with dates to absolute minimum (it's not truly required by the copyright law, but the interpretation of the law is a bit fuzzy, so we are keeping years in the main license files). So the first type is used only in the main license file and in the angular.io footer.

The second one is what I generally used everywhere, except for source code because I really don't want to touch hundreds if not thousands of files as we are landing all the Ivy PRs.

The third one comes from CLI - it's a golden file showing what the cli generates. I don't have control over that in this repo.

And the last one is the one I thought you missed, but of course you didn't. It's the notice in all source files in the repo. We'll need to find a good time to update these without disrupting day-to-day development too much. (it might be easier than it seems because the diff would unlikely collide, but the change is definitely out of scope for this PR).

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}