-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Did SpaceDock's GitHub CKAN user disappear? #188
Comments
I didnt delete anything. You could ping Thomas. I also might have missid to restart something at some point. |
Do you happen to know who created the Space-Duck user (i.e., was it someone from SpaceDock or CKAN)? Maybe GitHub auto-deleted it because of some rule about how bot accounts should be set up. Are there logfiles that could confirm that SpaceDock is still trying to create pull requests? There might be an error message that could indicate what happened. |
I created it, but I don't know which email I used anymore (might be a virtual mail address that redirected to VITAS mail account, or support@spacedock.info), so even if there is a notification, I don't know where it ended up. |
Hi, The server is running notify, mail and spacedock itself and it seems to send mails and notify (i can past logs if need be). Im planing to move all the things for some time now and i still want to but atm its still where it always was. I hope that helps. |
Oh wow we just got a backlog of 125 previously hidden pull requests! Looks like Space-Duck is back in business! Thanks for fixing this. |
Description
I think SpaceDock's CKAN checkbox is broken. We last received a pull request from SpaceDock in late May 2018; see this commit:
However, if you click on that commit's associated pull request, it doesn't seem to exist:
I think those pull requests used to be created by a GitHub user called
Space-Duck
? Who no longer exists? I hesitated to report this for a long time because I didn't know and couldn't find the official team history of it, but it's been quite a while since we've heard from SpaceDock's bot, so it's probably worth looking into.Please let us know if there's any info we can provide or anything we can do to help!
The text was updated successfully, but these errors were encountered: