# Synchronization after cloning repository

**URL:** <https://discourse.psychopy.org/t/synchronization-after-cloning-repository/33482>\
**Category:** Pavlovia Surveys\
**Created:** [February 22, 2023, 12:02pm UTC](https://discourse.psychopy.org/t/synchronization-after-cloning-repository/33482 "2023-02-22T12:02:43Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sarkadava](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.psychopy.org/sarkadava/32/35694_2.png) [@sarkadava](https://discourse.psychopy.org/u/sarkadava)\
**Post date:** [February 22, 2023, 12:02pm UTC](https://discourse.psychopy.org/t/synchronization-after-cloning-repository/33482/1 "2023-02-22T12:02:43Z")

</div>

I am running an experiment and want to change one small thing in a setting. Since the experiment was originally uploaded on different desktop, I had to clone the experiment (through GitHub) and I changed the issue and wanted to upload it back. While Github is able to push everything to the Gitlab repository and I can see the uploaded files, I cannot synchronize the project in PsychoPy, as I get following error:

File “C:\Users\Sarka Kadava\AppData\Local\Programs\PsychoPy\lib\site-packages\git\cmd.py”, line 983, in execute  
raise GitCommandError(redacted\_command, status, stderr\_value, stdout\_value)  
git.exc.GitCommandError: Cmd(‘C:\Users\Sarka Kadava\AppData\Local\Programs\PsychoPy\MinGit\cmd\git.exe’) failed due to: exit code(1)  
cmdline: C:\Users\Sarka Kadava\AppData\Local\Programs\PsychoPy\MinGit\cmd\git.exe pull [Wim Pouw / FLESH\_EXP\_1A · GitLab](https://oauth2: ***** @gitlab.pavlovia.org/wimpouw/flesh_exp_1a) master  
stderr: ‘fatal: Couldn’t find remote ref master  
warning: redirecting to [Wim Pouw / FLESH\_EXP\_1A · GitLab](https://gitlab.pavlovia.org/wimpouw/flesh_exp_1a.git/)’

Whether the sync in PsychoPy is necessary or not, I cannot see the change of my experiment when running it on Pavlovia. I don’t know whether that is because of the common problem with cache (?) or because of this error.  
Thanks for any suggestions for solution

---

<div class="post-metadata">

**Author:** ![JensBoelte](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.psychopy.org/jensboelte/32/9060_2.png) [@JensBoelte](https://discourse.psychopy.org/u/JensBoelte)\
**Post date:** [February 22, 2023, 2:22pm UTC](https://discourse.psychopy.org/t/synchronization-after-cloning-repository/33482/2 "2023-02-22T14:22:09Z")

</div>

Hello sarkadava

my procedure to get a deployed experiment for a new computer is different. I start PsychoPy on the new computer, select **Find existing study (at [pavlovia.org](http://pavlovia.org))**, select **Me** in the Search for projects online, and sync/create the experiment I want to copy to the new machine. Then I make the edits and sync them back to Pavlovia.

The problem you are facing is that there is no branch called master in your forked project, see here [github - git pull master with error: fatal: couldn't find remote ref master - Stack Overflow](https://stackoverflow.com/questions/64628893/git-pull-master-with-error-fatal-couldnt-find-remote-ref-master)

Best wishes Jens

---

<div class="post-metadata">

**Author:** ![wakecarter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.psychopy.org/wakecarter/32/5753_2.png) [@wakecarter](https://discourse.psychopy.org/u/wakecarter)\
**Post date:** [February 22, 2023, 2:38pm UTC](https://discourse.psychopy.org/t/synchronization-after-cloning-repository/33482/3 "2023-02-22T14:38:41Z")

</div>

I do the same. An important point is to sync before making changes when you have local copies in more than one location.

---

<div class="post-metadata">

**Author:** ![sarkadava](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.psychopy.org/sarkadava/32/35694_2.png) [@sarkadava](https://discourse.psychopy.org/u/sarkadava)\
**Post date:** [February 22, 2023, 2:59pm UTC](https://discourse.psychopy.org/t/synchronization-after-cloning-repository/33482/4 "2023-02-22T14:59:20Z")

</div>

I do it as you write but I get the same error when cloning/syncing. Then I see that the pulling was actually succesfull and I have the experiment in new folder - but when I open it and sync it, it agains throws the error. Besides that - the thing I want to change is a presentation limit (for presentation cap in shelf) but when I check the settings at this new cloned file, the change is already there. So I guess there is also some problem with Pavlovia noticing this change, because the presentation limit is still set on the old number when I run it

---

<div class="post-metadata">

**Author:** ![sarkadava](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.psychopy.org/sarkadava/32/35694_2.png) [@sarkadava](https://discourse.psychopy.org/u/sarkadava)\
**Post date:** [February 22, 2023, 3:22pm UTC](https://discourse.psychopy.org/t/synchronization-after-cloning-repository/33482/5 "2023-02-22T15:22:54Z")

</div>

An update: I created branch ‘master’ in my gitlab repository - now everything worked, I cloned, changed, synced, then within gitlab made a merge request and comitted changes from master branch to main. All good, but Pavlovia still doesn’t see the change in my presentation limit

---

<div class="post-metadata">

**Author:** ![wakecarter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.psychopy.org/wakecarter/32/5753_2.png) [@wakecarter](https://discourse.psychopy.org/u/wakecarter)\
**Post date:** [February 22, 2023, 3:49pm UTC](https://discourse.psychopy.org/t/synchronization-after-cloning-repository/33482/6 "2023-02-22T15:49:58Z")

</div>

If the change is visible in GitLab then try using an incognito tab or Ctrl-Shift-R to flush the cache.

---

<div class="post-metadata">

**Author:** ![sarkadava](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.psychopy.org/sarkadava/32/35694_2.png) [@sarkadava](https://discourse.psychopy.org/u/sarkadava)\
**Post date:** [February 23, 2023, 9:09am UTC](https://discourse.psychopy.org/t/synchronization-after-cloning-repository/33482/7 "2023-02-23T09:09:56Z")

</div>

Haha, yes, that worked! Thank you 🙂