-
Notifications
You must be signed in to change notification settings - Fork 24
Maintenance handoff #42
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@altendky I have granted you access to PyPI project |
Invitation for GitHub admin to this repository sent. 👍 |
I see it listed when I log in to PyPI and I see the settings tab on the GitHub repository page. Thanks. I guess there's also AppVeyor and Travis? How are those handled? (and while we're discussing it, maybe CircleCI as well) |
@nicoddemus, it looks like I've got access to settings on Travis for pytest-twisted now but not on AppVeyor. I do see something about pytestbot but it doesn't seem to get me pytest-twisted settings access. |
@nicoddemus, not that there's any rush here but would it make sense to shift the AppVeyor build into the pytestbot account/team/whatever now? The repo and the Travis tests are already owned by 'pytest'. I'm suspecting there aren't any secrets I need from the existing build. |
Sorry about the delay here, it seems this message slipped through the cracks. I've added @altendky please check that you have access. |
@nicoddemus it appears I do have permissions at https://travis-ci.org/pytest-dev/pytest-twisted/settings. Thanks. Now to see if I'm any good at managing a project... |
like... actually checking the right server. :[ |
@nicoddemus, no, I don't get a |
Please take another look now. 👍 |
Looks the same. I tried logging in fresh in an incognito window just in case. |
Argh I forgot to save. 😅 Please try again. |
Looks good, thanks. |
Uh oh!
There was an error while loading. Please reload this page.
#34 (comment)
@vtitor, I'll do what I can. I guess we'll need to get me full admin rights (or whatever they are called) to this repository and PyPI? I see that last time @nicoddemus was involved (#11). If there are other points we can add them below as well.
The text was updated successfully, but these errors were encountered: