- Notifications
You must be signed in to change notification settings - Fork1.5k
@cbrochtrup Add FIRE_PAGER environment variable for PAGER functionality#337
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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 visithttps://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️Googlers:Go here for more info. |
cbrochtrup commentedApr 27, 2021
@googlebot I signed it! |
Uh oh!
There was an error while loading.Please reload this page.
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. ℹ️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. ℹ️Googlers:Go here for more info. |
cbrochtrup commentedMay 4, 2021
@claui, since I added your suggestion can you sign the CLA please 😄 |
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. ℹ️Googlers:Go here for more info. |
claui commentedMay 4, 2021
@googlebot I consent. |
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. ℹ️Googlers:Go here for more info. |
claui commentedMay 4, 2021
@cbrochtrup I tried everything but it won’t let me. Google doesn’t like the email address GitHub has assigned to my suggestion. Feel free to revert my suggestion and re-apply it yourself. |
cbrochtrup commentedMay 7, 2021
Ah shoot, I'm sorry Google isn't accepting your cla. Thanks for your suggestion. |
Implementthis comment.
Fixes#188