#Auto-deploy on Github not working

26 messages · Page 1 of 1 (latest)

terse crescent
#

My branch is main, the github repo is public, the GitHub integration is enabled and all the permissions are granted. But when I push to main it doesn't auto-deploy. I can 'check for updates' and then update, but I'd like it to be automatic.

old stumpBOT
#

Project ID: a21be923-5623-4bcf-bae3-7fa0d2379288

terse crescent
#

a21be923-5623-4bcf-bae3-7fa0d2379288

rustic burrow
#

Hello,

Services deployed from templates do not auto deploy.

You would want to disconnect the source, and then reconnect your desired repo.

terse crescent
#

This wasn't created from a template, it was created with the Deploy from GitHub Repo command.

rustic burrow
#

If it has the Check for updates button, it was deployed from a template.

terse crescent
rustic burrow
#

I will take a look at your service and advise shortly.

rustic burrow
#

Yes this service was deployed from a template, this button only appears for services deployed from templates.

terse crescent
#

i genuinely didn't do that. i really did just deploy from a github project. but that project does have a railway.toml.

#

the deploying ... section shows when i deploy a different project from a template. but does not appear in the railway-start-simple case.

rustic burrow
#

Please try the advise I gave and let me know if it works!

terse crescent
#

Yeah, that works, but that's a terrible flow.

If I have a railway.toml that defines the start command:

  1. Deploy from github project (no I didn't use a template)
  2. Disconnect from the github project for no reason
  3. Reconnect to the same github project for no reason
  4. Rebuild and re-deploy no changes

If I don't have a railway.toml file:

  1. Deploy from github project (no I didn't use a template)
  2. Watch it deploy what will be a non-functional setup
  3. Alter the start command and re-deploy (requires an entire rebuild)
  4. Try to push to github and auto-deploy and ... it doesn't work So back to step 2 above where I have to disconnect again

Yeah, so it's not even an issue with their being a railway.toml file at all. This just seems to not-auto deploy unless you disconnect/reconnect to the same repo.

rustic burrow
#

A railway.toml file has no involvement in this flow.

terse crescent
#

that was a DIFFERENT project. I was just showing the different between a template generated project and one deployed from a github repo.

terse crescent
#

Here is a project I just generated from a repo: fd684663-de1c-41fb-bf22-0c3842bb6aaa

#

here is a screen capture (edited for time) that shows that's deployed from a repo and still has "Check for Updates"

oak mulch
# terse crescent

Railway probably thinks that you do not own that repository (it thinks it's a public repository from someone else). Instead of copying the entire URL, search for your repository name in the search bar and wait until it pops up as an option.

terse crescent
#

Ok, thanks.

oak mulch
rustic burrow
#

Yep thalles is correct, you are deploying your repo as if it was a public repo, thus deploying it as a template service.

oak mulch
#

well, he left

rustic burrow
#

!s