Auto-update Glitch code on new GitHub commits

The “Import from GitHub” is a great first start, but what I really want is for my Glitch code to auto-update whenever I push a new commit to my GitHub repo :star_struck:

1 Like

It has already been posted once I believe :

but I still support the idea, as configuration to auto update from GitHub by a specified interval :+1: .


I also need this feature. I don’t want to have to click Pull from Github every time I release new features to my repo. Thanks so much for the hard work. I love glitch.

We may add this feature in the future. In the meantime, you might like to know that GitLab supports git repo syncing so can already support this use-case. If you’re interested, I can supply setup steps.

1 Like

I would glad to get the setup instructions, TIA.

Take a look at


I have completed the setup but somethings didn’t seem clear at first but later figured it out. My source code originally is on Github so basically in order to get the auto update from glitch I need to change my remote origin url from github to gitlab so I push my changes to gitlab and no longer github, am I in the right direction?

That’s right, and once it’s on GitLab it will then be regularly synced from there to Glitch.

1 Like

I got this error when I push to my repo on gitlab and it tries to sync with glitch.

2:Gitlab::Git::CommandError: remote: error: refusing to update checked out branch: refs/heads/master
remote: error: By default, updating the current branch in a non-bare repository
remote: error: is denied, because it will make the index and work tree inconsistent
remote: error: with what you pushed, and will require ‘git reset --hard’ to match
remote: error: the work tree to HEAD.
remote: error:
remote: error: You can set ‘receive.denyCurrentBranch’ configuration variable to
remote: error: ‘ignore’ or ‘warn’ in the remote repository to allow pushing into
remote: error: its current branch; however, this is not recommended unless you
remote: error: arranged to update its work tree to match what you pushed in some
remote: error: other way.
remote: error:
remote: error: To squelch this message and still keep the default behaviour, set
remote: error: ‘receive.denyCurrentBranch’ configuration variable to ‘refuse’.
! [remote rejected] master → master (branch is currently checked out)
error: failed to push some refs to ‘[FILTERED]’