"Sync could not create webhook" after repo transfer

[prabhav]

Hi there!

I had Siteleaf setup with the GitHub repo studiodbj/lisamarierunfola which was publishing to Netlify. I recently transferred the repo to an organization account and it now lives under lisamarierunfola/lisamarierunfola. I also transferred ownership of Siteleaf to another user but remained an "Admin" myself. When I went to the "Sync" tab under Settings in Siteleaf to change the repo, I kept getting the error "Sync could not create GitHub webhook, check your repo settings". I went ahead and removed the existing Siteleaf webhook on the repo, so that it can create a new one — but I still kept getting the error.

I even tried creating a new Siteleaf site and linking that with the new repo, but got the same error.

How can I resolve this issue? Let me know if I can provide any additional details that would help.

Not sure if this helps, but I get this error when trying to publish any new changes. I'm guessing this just means that Siteleaf can't find a repo at the previous address.

[sskylar]

Do you know if the organization has given you Read, Write, or Admin privileges to the repo? You will need Admin privileges in order to create the proper webhooks and sync with the organization's repo.

Here's what I would suggest next:

1. In GitHub, locate your "Authorized OAuth Apps": https://github.com/settings/applications
2. Click on "Siteleaf" in this list.
3. Under "Organization access" confirm your org has a green checkmark next to it. If not, you can either click Grant or Request to gain access.

Note: Instead of authenticating with your personal account, you could also to set up a machine user for your site — essentially a new user that only has Admin access to this single repository, which will keep things extra secure. In that case, you can log out of github.com and reconnect through Siteleaf's Sync settings with the new user.

Hope that helps!

[prabhav]

Thanks so much for such a detailed and helpful response, @sskylar! I really appreciate it.

I went ahead and followed the steps you laid out and it solved the issue!

[sskylar]

Glad to hear!