Tails won’t publish to gihub
Tails app won’t publish it GitHub.
Hey Bobby. Sorry to bother you again. Or whoever this may be. Tails is acting weird. It will tell me my GitHub publishing settings test is successful but when I go to publish it tells me something is wrong and won’t send it? It hasn’t worked since it’s initial commit over a month ago. I haven’t needed to alter it until today.
It also won’t let me save my work now. It says ‘sending webhook’ but it never goes anywhere.
1
Hey there!
Which project is this related to? Will try to replicate this on my end as well to see if the issue is reproducible.
I'll take a look and also bring it up to Tony as well!
Hey Keith,
Can you double check that your Github Personal Access Token has not expired. I actually went to test this out on an old project was not able to publish to Github and I realized it was because the Access Token that I submitted had expired.
You should be able to see it by clicking Edit Publishing Source
And then you'll want to update the Personal Access Token with an updated access token.
Give that a try and let me know if it works. If not, we can investigate the issue further :)
Thanks! Talk to you soon.
Hey guys, its for the Shop-4-charities project. I am pushing to a branch called tails in the repo. Should I be pushing to the main branch instead? Also, GitHub has fine grained tokens which is beta and classic tokens. I assume I am supposed to use the classic?
I just changed my access token again and it still wont publish it. I originally used the beta tokens and it initially did commit but won’t now.
I have no issues using the tails app in my local laravel wave installation and works seamlessly. That is always an option. Just inserting it directly into my project.
Hey!
I think I know what the problem is, you are trying to deploy to a repository that already contains your Wave files. That would not really work.
The idea behind deploying to GitHub is to deploy to a plain repository where you would only have that specific Tails site so you could use it with GitHub Pages.
If you want to deploy to your Wave project, then you should use the Tails Laravel package instead:
Hope that this helps!
Right but what does wave have to do with publishing tails? You can publish to any repo, regardless of content already there?
Most likely as you already have content in that repo and other commits, there are some merge conflicts happening. You should be able to see the commits in the commit history for more information.
Can you share more information why would you need those static files commuted in the same repo as an existing Laravel app?
Yeah, it would probably be best to push to it's own repo just incase. Up to you, but you should be able to define which branch in the Publish Settings.
Bobby and I did see an error message come through that we are investigating on this. Would you be able to try and create a new branch and deploy to that one.
I would use the Classic token and allow all repo permissions for the token. We'll keep you posted on what we find.
Thanks.
Sorry it took me so long I got stuck on implementing google analytics.
I see the error I made when making the tails branch, I didn’t delete the wave app out of the branch. Oddly enough though, when I publish to the empty repo I originally used, it published no problem.
I wonder why it does that? I have no branch protections and that repo has not had any commits except one over a month ago so I am really confused why it wouldn’t work but alas, I no longer need it. I will just roll with the original repo.
The idea behind it was to eventually put the real app besides the tails repo.
Any news on that error you found?
Hey,
For the time being it’s best to use an empty branch, otherwise it might not work as expected.
Have you tried this with an empty branch?
Oh i was referring to Tonys post about him and you finding an error on your end.
It worked just fine when I changed the publishing source back to the original repo I used that only contained tails.