Git Manager: Remotes and Sync
Connect remotes, read ahead/behind sync cues, use fetch and refresh from the actions & options menu, and handle pull/push safely in the experimental Git Manager.
The toolbar tells you whether the repository is connected
Git Manager uses the toolbar to make remote state visible. Before any remote is configured, Connect to Remote Repository is the important button. Once a remote exists, Pull and Push replace it as sync-status controls and can show behind or ahead counts when tracking is active. The branch button still stays on the left because sync is always about the current branch, and during merge state Continue Merge and Abort Merge take over so you finish the risky state before doing more remote work.
Connect first, authenticate when needed
Connect to Remote Repository is the first remote-state button you see. Use it to register the remote URL and let Git Manager create the default origin entry. Authentication is delayed until the first real network operation, so setup stays quick while still supporting GitHub, GitLab, Bitbucket, generic HTTPS remotes, and SSH remotes.
Refresh and Fetch live in the actions & options menu
The actions & options menu is the lightweight remote maintenance surface in the current manager. Refresh is always there, and manual Fetch appears when remotes exist so you can update remote-tracking refs on demand instead of waiting for the background fetch cycle. Treat that menu as the place to refresh your picture of the remote before deciding whether to pull or push.
Pull first to catch up, push when your local branch is ready
Pull and Push are not symmetric decoration. Pull is the catch-up button: it brings the latest remote commits into your local branch and can start a merge, so Git Manager checks whether the working tree is safe before it begins. Push is the publish button: it sends the commits you already made locally once the branch is truly ahead and the working tree is in a shareable state. The ahead and behind counts explain why one of those buttons matters right now.
Sync changes the history view you are reading
After a successful sync, read the result in the history list and refs instead of relying on a toast alone. After pull, you should see incoming commits appear and remote-tracking refs move. After push, the local and remote refs line up again. Advanced mode makes that easiest to verify because it shows how the remote branch moved relative to your local branch.
A pull may turn into a merge workflow
If pull brings in overlapping work, the toolbar changes meaning immediately. Continue Merge becomes the forward path once conflicts are resolved, while Abort Merge is the escape hatch if you need to abandon the merge attempt. Normal branch switching and sync actions are suppressed in that state so you do not stack more risky operations on top of an unresolved repository.
Continue with the related Git topic
Remote work is easiest to reason about once you also understand the branch model and the history model behind it.
