Skip to content

Conversation

Lucaman99
Copy link
Contributor

Sorry for opening another PR, but the CLA in the other request simply won't go through. This takes into account a lot of the changes requested in #1934.

@googlebot
Copy link

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.

@Lucaman99
Copy link
Contributor Author

Also @Strilanc, I made all of the requested changes to built-in Cirq functions, however, wasn't able to find documentation for the Cirq ArithmeticOperations class. As a result, this is the one change I haven't made yet, is this a fairly new feature?

@vtomole
Copy link
Collaborator

vtomole commented Dec 18, 2019

@Lucaman99 Sign the CLA. Otherwise we could override; which means the old pull request is fine to use for these new changes.

@Lucaman99
Copy link
Contributor Author

I have, but it's saying that "co-contributors" to this commit haven't signed it, which is likely due to me accidentally using a different email when I made some of the commits a couple months back

@Lucaman99
Copy link
Contributor Author

"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."

@Lucaman99
Copy link
Contributor Author

@googlebot I fixed it.

@vtomole vtomole requested a review from Strilanc December 18, 2019 20:01
@vtomole
Copy link
Collaborator

vtomole commented Jan 8, 2020

@Lucaman99 The reason we have this new pull request is to get past this CLA issue. Squash these commits so this pull request doesn't contain the non-CLA.

@Lucaman99
Copy link
Contributor Author

Squash all the commits previous to the most recent one?

@vtomole
Copy link
Collaborator

vtomole commented Jan 16, 2020

@Lucaman99 Yes, then change the commit email to the primary one on your GitHub account (https://stackoverflow.com/a/3042512/5716192).

When you Cirq$ git config --list, is the user.email the primary one in your Github account?

@Lucaman99
Copy link
Contributor Author

Hi @vtomole! Just wanted to ping you in case you hadn't seen this yet, I made the requested changes last week. Let me know when you get the chance to take a look! 🙂

@@ -0,0 +1,57 @@
# Licensed under the Apache License, Version 2.0 (the "License");
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You missed removing this file: . See #2657 (comment)

@Lucaman99
Copy link
Contributor Author

@vtomole Sorry about that, I just deleted it

Copy link
Collaborator

@vtomole vtomole left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Rename notebook_tutorials to notebooks and we'll merge it in.

@Lucaman99
Copy link
Contributor Author

Done!

@vtomole
Copy link
Collaborator

vtomole commented Mar 9, 2020

Hey @dstrain115, You'll need to manually add the cla for us to merge this.

@dstrain115 dstrain115 added cla: yes Makes googlebot stop complaining. and removed cla: no labels Mar 9, 2020
@googlebot
Copy link

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.)

ℹ️ Googlers: Go here for more info.

@dstrain115
Copy link
Collaborator

Added the CLA manually. Hopefully that fixes things.

You may want to make sure that all your environments are set up with the same git author so that this doesn't complain in the future.

@googlebot
Copy link

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.

@googlebot googlebot added cla: no and removed cla: yes Makes googlebot stop complaining. labels Mar 9, 2020
@@ -0,0 +1,123 @@
{
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this file

@Lucaman99
Copy link
Contributor Author

Ok, done

@vtomole
Copy link
Collaborator

vtomole commented Mar 9, 2020

@Lucaman99 Looks like my merge voided the cla. I think this is what we should do: copy these files into a new branch and commit them with the email address with which you signed the cla and open a new pull request.

@Lucaman99
Copy link
Contributor Author

Sounds good, I'll do that right now

@Lucaman99 Lucaman99 closed this Mar 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants