-
Notifications
You must be signed in to change notification settings - Fork 2
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
Move to @octokit org #80
Comments
Ping @gr2m @nickfloyd @kfcampbell Can you help out with transfering this to the Octokit org |
Hey @wolfy1339 Can you give us admin access to this repo so that we can take the first step and move this over to the octokit org? |
Sure thing |
Looks like I just got push access... just to confirm you want this to be a complete hoist and move to @octokit correct? If so I'll need access to settings as well. |
Yup, a complete move. I haven't been able to find the proper setting for giving admin access. All I can see is either inviting collaborator, or removing them. I have searched the docs to no avail. It only refers to collaborators for personal repositories |
Ok... have you attempted to transfer ownership under settings > General > Transfer Ownership Then choose the Then enter in |
That doesn't work.
|
When you click on |
Cool... you should now be able to follow the steps above. |
Those steps are still not working, with the same message
|
Giving someone admin rights in a personal repository is not supported |
Let me have a look at your permissions on the octokit org. Sorry for all of this trouble @wolfy1339. As a side note: I've added you as a moderator (that was just an oversight you should've always been a mod, apologies for that). |
Ok.. someone smarter than me came up with a workaround - I've added you to the octokit-transfers org. You'll have admin access there and then we can move the repo to it's final destination under octokit. So sorry for all of this complexity... hopefully we can get everything moved. |
Alright that works! Moved it |
It has been transferred to the octokit org 🥳 https://github.com/octokit/openapi-webhooks |
It seems some things need tweaking, the release process failed. Seems like the token possibly isn't set |
I believe this should fix it |
Really great work on this, thank you @wolfy1339!! |
In order to move this repository and it's packages to the Octokit org, as discussed in octokit/webhooks.js#841
This will be used in the next major version of
@octokit/webhooks
@octokit/openapi-webhooks
,@octokit/openapi-webhooks-types-*
and release new versionswolfy1339/openapi-webhoks-legacy
. That way https://github.com/wolfy1339/openapi-webhooks will continue to redirect to the new https://github.com/octokit/openapi-webhooks@octokit/openapi-webhooks
as the sole dependency for@wolfy1339/openapi-webhooks
@wolfy1339/openapi-webhooks
and@wolfy1339/openapi-webhooks-types-*
packages on npmThe text was updated successfully, but these errors were encountered: