[pull] master from JuliaRegistries:master by pull[bot] · Pull Request #49 · dgfug/General

pull · 2021-11-11T22:44:53Z

See Commits and Changes for more details.

Can you help keep this open source service alive? 💖 Please sponsor : )

google-cla · 2021-11-11T22:45:30Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-11T22:50:26Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-11T23:00:56Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-11T23:01:13Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-11T23:25:22Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-11T23:49:07Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T00:26:01Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T00:57:44Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T00:58:01Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T01:09:47Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T01:22:04Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T03:33:24Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T04:29:50Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T06:02:15Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T06:37:53Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T06:38:16Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T06:49:23Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T07:49:51Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T08:14:49Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T08:50:54Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T09:14:59Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T09:23:31Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T09:36:08Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T09:47:57Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T10:12:02Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T10:57:17Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T11:45:27Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T11:45:43Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T11:57:22Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

UUID: 4de3b72a-362e-43dd-83ff-3f381eda9f9c Repo: https://github.com/JoeyT1994/TensorNetworkQuantumSimulator.jl.git Tree: f2d761f9c09e69478f03a59bb22430cfa31482b4 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 3caadacf-3504-43fd-90cf-12adede613ab Repo: https://github.com/subhk/Tarang.jl.git Tree: 0f6c1b5a7a56ad2f346ba8ff2fa90b483d97cf65 Registrator tree SHA: 3e66fa3f5110ad24f2ce227d4bf2d86af116b963 Co-authored-by: JuliaHubRegistrator <juliahub-registrator@juliacomputing.com>

UUID: cbdf2221-f076-402e-a563-3d30da359d67 Repo: https://github.com/MakieOrg/AlgebraOfGraphics.jl.git Tree: 0b636a41e46bdf077773713c17154e1ea21678fc Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 94d474ba-9a8a-4612-aaf4-76c1836fe059 Repo: https://github.com/almost6heads/ConleyDynamics.jl.git Tree: 7d36182f47543bfdaca3da353656a69cdef12f9d Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 1244ff17-1aa7-4121-9347-f4ead108e58f Repo: https://github.com/ghyatzo/OptParse.jl.git Tree: 3c642a8706709fb9e8c2c75f75093c4e12ad3151 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 3ed48883-6809-43ec-b77a-d23b0650d8c4 Repo: https://github.com/yufongpeng/ChemistryQuantitativeAnalysis.jl.git Tree: a7b966587143b4376824225b88cf090c29ff3abf Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 90b8fcef-0c2d-428d-9c56-5f86629e9d14 Repo: https://github.com/JuliaDataCubes/YAXArrayBase.jl.git Tree: 5bc84454deee9f755b53b82390d2870bd5c87889 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: aa815940-ac17-4642-b6b9-9c066aae69b2 Repo: https://github.com/myersm0/UniversalDependencies.jl.git Tree: a16ca46e1f578881f7a3cd82e2a66d993e1a83d4 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: fdbf4ff8-1666-58a4-91e7-1b58723a45e0 Repo: https://github.com/JuliaData/XLSX.jl.git Tree: 53f4cdd9df3380ed5166b84cf5a8ccec6442f93d Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 23e940aa-d356-45ed-adbd-bebf2015d7d9 Repo: https://github.com/Klafyvel/InstanceDispatch.jl.git Tree: 60ae9095213748cab624df231277dc3073839ce5 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 0a96183e-380b-4aa6-be10-c555140810f2 Repo: https://github.com/JuliaAI/MLJModelRegistryTools.jl.git Tree: 7768b769a518d91725ff83a7fbc58b966fd57625 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: ed894a53-35f9-47f1-b17f-85db9237eebd Repo: https://github.com/WaterLily-jl/WaterLily.jl.git Tree: 1f79bd1b738c67dc2b102e167030807a9c0b7c8a Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: fbca939-dd0a-4d1c-b066-ae75f6ef1ad5 Repo: https://github.com/mlesnoff/Jchemo.jl.git Tree: c7df1b0c6e760868e07f49421b72a5955241ce6f Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: c6b3b713-2a2b-4e07-a35c-d57ac4f46186 Repo: https://github.com/raphasampaio/UnsupervisedClustering.jl.git Tree: f5c07cf114193e4b9dca7f92dfc852a2f56315e3 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

The repository has moved from YingboMa/FastBroadcast.jl to SciML/FastBroadcast.jl. Co-authored-by: ChrisRackauckas-Claude <accounts@chrisrackauckas.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

UUID: 2b5f629d-d688-5b77-993f-72d75c75574e Repo: https://github.com/SciML/OrdinaryDiffEq.jl.git Tree: c5fe5125fcba8f98cdc5c7221b6c324883899c07 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 49048992-29d2-5fd1-994f-9cecf112d624 Repo: https://github.com/JuliaBinaryWrappers/cunumeric_jl_wrapper_jll.jl.git Tree: f0f0ee828657b298b0e3fb5cc103cc69268a1087 Registrator tree SHA: 3e66fa3f5110ad24f2ce227d4bf2d86af116b963

UUID: 7034ab61-46d4-4ed7-9d0f-46aef9175898 Repo: https://github.com/SciML/FastBroadcast.jl.git Tree: b693851aca57cc74652f0297d24ff0e29ca1dc49 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 6e093c14-372f-5516-b4d7-a6ce14f1038b Repo: https://github.com/JuliaBinaryWrappers/legate_jl_wrapper_jll.jl.git Tree: c63cea26f109f4ddfce51b2de7305cdb18afa131 Registrator tree SHA: 3e66fa3f5110ad24f2ce227d4bf2d86af116b963

UUID: b41c07a2-2abb-11e9-070a-c3c1b239e7df Repo: https://github.com/PerezHz/NEOs.jl.git Tree: 6c871fc8a50d79155848fbd8f8f488cf59716209 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 038fdbe3-3777-5af9-9568-3738956aeb97 Repo: https://github.com/JuliaBinaryWrappers/juliaup_jll.jl.git Tree: 819e2ac391bd8b2438f07c38381ba7389b2f1e68 Registrator tree SHA: 3e66fa3f5110ad24f2ce227d4bf2d86af116b963

UUID: 1ed8b502-d754-442c-8d5d-10ac956f44a1 Repo: https://github.com/SciML/SciMLSensitivity.jl.git Tree: d94f224a2e7d5a7a5cc6a0abb64323fcf8076fb1 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 731186ca-8d62-57ce-b412-fbd966d074cd Repo: https://github.com/SciML/RecursiveArrayTools.jl.git Tree: 76a9c4d3f7b256dd34074e714ffe0ced8d3d21de Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: c4671d76-df94-11ed-2057-43d4fd632fad Repo: https://github.com/harmoniqs/Piccolo.jl.git Tree: 4d769b6bd2c0977b973c0b4364c48113834181b2 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 0192cb87-2b54-54ad-80e0-3be72ad8a3c0 Repo: https://github.com/EnzymeAD/Reactant_jll.jl.git Tree: fbfefbebb571be9da9649193f4daafcd48bebe35 Registrator tree SHA: 3e66fa3f5110ad24f2ce227d4bf2d86af116b963 Co-authored-by: enzymead-bot[bot] <238314553+enzymead-bot[bot]@users.noreply.github.com>

UUID: 4dedf8fe-8d9a-5fb8-8563-19379e8d5c54 Repo: https://github.com/JuliaBinaryWrappers/MQLib_jll.jl.git Tree: e9d0ece06d3153d58fb184e7a9ab29e4aa65da5f Registrator tree SHA: 3e66fa3f5110ad24f2ce227d4bf2d86af116b963

UUID: b9b1ffdd-6612-4b69-8227-7663be06e089 Repo: https://github.com/JuliaActuary/FinanceCore.jl.git Tree: 40e06452d861ac6e38e071b7edfa5b61e5a6f04e Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 7034ab61-46d4-4ed7-9d0f-46aef9175898 Repo: https://github.com/SciML/FastBroadcast.jl.git Tree: a1d412040dd21720711da6780ee1d767f60cde28 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

UUID: 9ea80cae-fc13-4c00-8066-6eaedb12f34b Repo: https://github.com/ProjectTorreyPines/FastInterpolations.jl.git Tree: 96cbce6d384b0c98b237c35bebea655771424dfd Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

pull bot added the ⤵️ pull label Nov 11, 2021

Registrator and others added 30 commits March 30, 2026 14:07

New version: TensorNetworkQuantumSimulator v0.3.2 (#151717)

bbb869b

UUID: 4de3b72a-362e-43dd-83ff-3f381eda9f9c Repo: https://github.com/JoeyT1994/TensorNetworkQuantumSimulator.jl.git Tree: f2d761f9c09e69478f03a59bb22430cfa31482b4 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: AlgebraOfGraphics v0.12.6 (#151718)

638027d

UUID: cbdf2221-f076-402e-a563-3d30da359d67 Repo: https://github.com/MakieOrg/AlgebraOfGraphics.jl.git Tree: 0b636a41e46bdf077773713c17154e1ea21678fc Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: ConleyDynamics v0.6.1 (#151719)

55a9943

UUID: 94d474ba-9a8a-4612-aaf4-76c1836fe059 Repo: https://github.com/almost6heads/ConleyDynamics.jl.git Tree: 7d36182f47543bfdaca3da353656a69cdef12f9d Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: OptParse v0.1.5 (#151701)

0400967

UUID: 1244ff17-1aa7-4121-9347-f4ead108e58f Repo: https://github.com/ghyatzo/OptParse.jl.git Tree: 3c642a8706709fb9e8c2c75f75093c4e12ad3151 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: ChemistryQuantitativeAnalysis v0.9.4 (#151720)

18321ad

UUID: 3ed48883-6809-43ec-b77a-d23b0650d8c4 Repo: https://github.com/yufongpeng/ChemistryQuantitativeAnalysis.jl.git Tree: a7b966587143b4376824225b88cf090c29ff3abf Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: YAXArrayBase v0.7.10 (#151721)

b6a9e48

UUID: 90b8fcef-0c2d-428d-9c56-5f86629e9d14 Repo: https://github.com/JuliaDataCubes/YAXArrayBase.jl.git Tree: 5bc84454deee9f755b53b82390d2870bd5c87889 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: UniversalDependencies v0.2.0 (#151722)

d80e129

UUID: aa815940-ac17-4642-b6b9-9c066aae69b2 Repo: https://github.com/myersm0/UniversalDependencies.jl.git Tree: a16ca46e1f578881f7a3cd82e2a66d993e1a83d4 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: XLSX v0.11.1 (#151723)

3c784ad

UUID: fdbf4ff8-1666-58a4-91e7-1b58723a45e0 Repo: https://github.com/JuliaData/XLSX.jl.git Tree: 53f4cdd9df3380ed5166b84cf5a8ccec6442f93d Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: InstanceDispatch v0.3.1 (#151724)

11c19c1

UUID: 23e940aa-d356-45ed-adbd-bebf2015d7d9 Repo: https://github.com/Klafyvel/InstanceDispatch.jl.git Tree: 60ae9095213748cab624df231277dc3073839ce5 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: MLJModelRegistryTools v0.1.4 (#151726)

adabd28

UUID: 0a96183e-380b-4aa6-be10-c555140810f2 Repo: https://github.com/JuliaAI/MLJModelRegistryTools.jl.git Tree: 7768b769a518d91725ff83a7fbc58b966fd57625 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: WaterLily v1.6.0 (#151727)

4bacc43

UUID: ed894a53-35f9-47f1-b17f-85db9237eebd Repo: https://github.com/WaterLily-jl/WaterLily.jl.git Tree: 1f79bd1b738c67dc2b102e167030807a9c0b7c8a Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: Jchemo v0.9.6 (#151728)

7ba7171

UUID: fbca939-dd0a-4d1c-b066-ae75f6ef1ad5 Repo: https://github.com/mlesnoff/Jchemo.jl.git Tree: c7df1b0c6e760868e07f49421b72a5955241ce6f Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: UnsupervisedClustering v0.4.5 (#151729)

697e75b

UUID: c6b3b713-2a2b-4e07-a35c-d57ac4f46186 Repo: https://github.com/raphasampaio/UnsupervisedClustering.jl.git Tree: f5c07cf114193e4b9dca7f92dfc852a2f56315e3 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

Update FastBroadcast repo URL to SciML org (#151731)

2665964

The repository has moved from YingboMa/FastBroadcast.jl to SciML/FastBroadcast.jl. Co-authored-by: ChrisRackauckas-Claude <accounts@chrisrackauckas.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

New version: DiffEqBase v6.213.0 (#151730)

2877e6a

UUID: 2b5f629d-d688-5b77-993f-72d75c75574e Repo: https://github.com/SciML/OrdinaryDiffEq.jl.git Tree: c5fe5125fcba8f98cdc5c7221b6c324883899c07 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

Update DWaveNeal repository URL (#151578)

86cb20f

New version: FastBroadcast v1.0.0 (#151732)

6a4ada5

UUID: 7034ab61-46d4-4ed7-9d0f-46aef9175898 Repo: https://github.com/SciML/FastBroadcast.jl.git Tree: b693851aca57cc74652f0297d24ff0e29ca1dc49 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: legate_jl_wrapper_jll v25.10.3+1 (#151734)

6b817c8

UUID: 6e093c14-372f-5516-b4d7-a6ce14f1038b Repo: https://github.com/JuliaBinaryWrappers/legate_jl_wrapper_jll.jl.git Tree: c63cea26f109f4ddfce51b2de7305cdb18afa131 Registrator tree SHA: 3e66fa3f5110ad24f2ce227d4bf2d86af116b963

New version: NEOs v0.24.6 (#151736)

70dd783

UUID: b41c07a2-2abb-11e9-070a-c3c1b239e7df Repo: https://github.com/PerezHz/NEOs.jl.git Tree: 6c871fc8a50d79155848fbd8f8f488cf59716209 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: juliaup_jll v1.19.9+0 (#151737)

13cb603

UUID: 038fdbe3-3777-5af9-9568-3738956aeb97 Repo: https://github.com/JuliaBinaryWrappers/juliaup_jll.jl.git Tree: 819e2ac391bd8b2438f07c38381ba7389b2f1e68 Registrator tree SHA: 3e66fa3f5110ad24f2ce227d4bf2d86af116b963

New version: SciMLSensitivity v7.100.0 (#151739)

3a977de

UUID: 1ed8b502-d754-442c-8d5d-10ac956f44a1 Repo: https://github.com/SciML/SciMLSensitivity.jl.git Tree: d94f224a2e7d5a7a5cc6a0abb64323fcf8076fb1 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: RecursiveArrayTools v3.50.0 (#151740)

86d706b

UUID: 731186ca-8d62-57ce-b412-fbd966d074cd Repo: https://github.com/SciML/RecursiveArrayTools.jl.git Tree: 76a9c4d3f7b256dd34074e714ffe0ced8d3d21de Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: Piccolo v1.7.0 (#151742)

624810f

UUID: c4671d76-df94-11ed-2057-43d4fd632fad Repo: https://github.com/harmoniqs/Piccolo.jl.git Tree: 4d769b6bd2c0977b973c0b4364c48113834181b2 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: MQLib_jll v0.1.1+0 (#151746)

5902988

UUID: 4dedf8fe-8d9a-5fb8-8563-19379e8d5c54 Repo: https://github.com/JuliaBinaryWrappers/MQLib_jll.jl.git Tree: e9d0ece06d3153d58fb184e7a9ab29e4aa65da5f Registrator tree SHA: 3e66fa3f5110ad24f2ce227d4bf2d86af116b963

New version: FinanceCore v2.4.1 (#151747)

870687d

UUID: b9b1ffdd-6612-4b69-8227-7663be06e089 Repo: https://github.com/JuliaActuary/FinanceCore.jl.git Tree: 40e06452d861ac6e38e071b7edfa5b61e5a6f04e Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: FastBroadcast v1.1.0 (#151748)

3094c32

UUID: 7034ab61-46d4-4ed7-9d0f-46aef9175898 Repo: https://github.com/SciML/FastBroadcast.jl.git Tree: a1d412040dd21720711da6780ee1d767f60cde28 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

New version: FastInterpolations v0.4.7 (#151750)

97db132

UUID: 9ea80cae-fc13-4c00-8066-6eaedb12f34b Repo: https://github.com/ProjectTorreyPines/FastInterpolations.jl.git Tree: 96cbce6d384b0c98b237c35bebea655771424dfd Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3

Conversation

pull bot commented Nov 11, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

google-cla bot commented Nov 11, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 11, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 11, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 11, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 11, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 11, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

Uh oh!

google-cla bot commented Nov 12, 2021

pull bot commented Nov 11, 2021 •

edited

Loading