Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

I can clone my repositories but I cannot push to GitLab

silbongio
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 29, 2023

I have reset my MacBook Pro to factory settings. I reinstalled Source Tree.

I was able to clone my repositories, but when I try to push to gitlab, it doesn't do it. I do not get an error message, it just never completes the push. 

If I am able to clone repositories, why can't I push? 

Any reasons why this is going on?

1 answer

0 votes
Martin Runge
Community Champion
July 7, 2026

Hi @silbongio

Welcome to the Atlassian community!

Being able to clone to your own repos but not to GitLab specifically suggests credentials rather than Sourcetree itself, since cloning only requires read access, whereas pushing requires write access to succeed.

I would check that the GitLab account added under Tools > Options > Authentication has a personal access token with write_repository scope, not just read. A token scoped to read-only would explain a push that hangs or does nothing, rather than showing a clear permission error.

I would also confirm the push is not just stuck waiting on 2FA or an SSH passphrase prompt hidden behind the main window, which is common right after a fresh macOS install where Keychain has no saved credentials yet. If you are using SSH, try pushing that same repo from Terminal with git push, since that tells you immediately whether this is a Sourcetree UI issue or a real auth failure with GitLab.

(?) Are you connecting over HTTPS or SSH, and does the push spinner just sit there forever, or does it eventually time out?

Cheers,
Martin

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events