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
GitHub webhook deployment not working. #25
Comments
Thanks for the kind words, @Codeize! The In the meantime, is it possible someone on your team removed the webhook? I'd be happy to remove your repo from the DB for a fresh start. If that sounds good, what's your repo called? |
Hmmm, maybe when testing I could have messed something up, sorry for the hassle if so. My repo is called Appreciate your fast response! |
Ah ok, this is an edge case - What's your Linear team name (feel free to DM me on Twitter or edit this afterwards)? Otherwise, should be ready to try re-syncing from scratch. Data dashboard is on the roadmap! |
My Linear team name was changed since I first tried to setup SyncLinear, it was called Engineering I believe, now it's called I also tried to re-sync and it still hasn't created the webhook GitHub-side. |
This was resolved after quite some back and forth between myself and Ted, essentially Ted had to delete my DB data and I had to delete and recreate a few webhooks. Really weird issue that still has no real clear explanation, but thanks for the help Ted, excited to see where this project can go :) |
Hey there team, thanks for this project, seems very cool!
An issue I've faced while trying to get setup is that the
Deploy Webhook
button seems to be already deployed when I go to deploy the GitHub webhook on my repo, but when I look in the Webhook settings of the GitHub repo there is no SyncLinear webhook, there is however a Discord one I use to relay events, it may be possible that it's conflicting with the setup?I'm not sure if this is something I've broken accidentally, but I've followed the steps that were detailed so not really sure where I went astray, if it was me.
Thanks!
The text was updated successfully, but these errors were encountered: