Sync several repositories: fetch, pull, push and rejected push

In the navigator, switch to the Git view: each project of the workspace shows its current branch and its ↑ (local commits to publish) and ↓ (remote commits to integrate) counters. A warning icon flags a repository that needs your attention.

Expand a project to see its unstaged, untracked and staged files, its stashes and worktrees, and commit from the composer at the bottom of the panel. A background fetch keeps the counters up to date.

Hover a project to reveal its actions: Fetch downloads remote references without touching your files, Pull integrates the upstream branch — by merge or rebase depending on the divergence — and Push publishes your commits. The … menu gathers the repository’s other actions.

You can sync several repositories in a row without opening their cockpit. A notification confirms each operation, for example “Pushed to origin – 4 commits”. For the cockpit details, see working with the remote.

If the remote branch moved ahead, Git refuses the push. Singularity opens the Push rejected — “main” is behind the remote dialog with three choices:

• Pull first integrates the remote changes locally so you can check them before pushing again. This is the safe choice.
• Force push replaces the remote branch with your local history using --force-with-lease.
• Cancel leaves both branches unchanged.

If the recovery fails in turn, Singularity offers a repair ticket. For GitHub workflows, it can also repair a broken SSH configuration.

Agents work in their own worktrees and the commit queue integrates their work one ticket after another, by rebase, without merge commits. Your main branch can therefore move while you work: Fetch before pushing, and prefer Pull first over a force push on a shared branch.