kyua
kyua copied to clipboard
freebsd
Update Fedora instructions
@jmmv also would be nice if you could do fedpkg retire for kyua-cli and kyua-testers.
W00t! Somebody (you?) packaged repackaged Kyua as a new RPM? Thanks! I opened a bug a long time ago with a preliminary spec but never got a responsive reviewer for it :-(
@jmmv I will add you as admins ;) and don't hesitate to improve it ;)
@googlebot rescan
(Mass-triggering a rescan of all open PRs as I have just configured automated CLA checks but the bot won't go through the backlog on its own.)
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).
:memo: Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. 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.
@jmmv why do you need CLA? :/
This is a Google sponsored project, so one needs to sign the Google CLA in order to contribute to it.
