Search the field guide

Search all 29 chapters. Your search stays on this device.

↑ ↓ Move between results Enter Open · Esc Close

Browse chapters

DocsEveryday GitFIELD NOTES / 13

Everyday Git · 1 min read

Syncing: fetch, pull and push

Preview documentation About this guide ⓘ

GitTrail is in preview: commands and features may change before the first release, and host integrations are still being tested against each live service.

Chapter 13 of 29
On this page

In this chapterChoose fetch, pull or push and understand the sync status.

GitTrail never fetches, pulls or pushes on its own. Every sync starts with your click, and shows progress you can cancel.

  • Sync status: up to date, to pull, to push, diverged, not published or gone, and when it was last checked.
  • Fetch, pull, pull with rebase, push, publish, and push tags.
  • Safe force push: refuses if someone else pushed in the meantime.
  • Remotes: add, rename, change address, remove, fetch one; Push here makes a remote the default for pushing.
  • Forks: add the original as upstream, see how far behind you are, bring its work in, or sync your fork on GitHub.
  • Push to several remotes at once.
  • In every repo: pull, fetch or switch branch across a workspace.
  • Network: proxy and company certificate per host.
  • Notifications when a long sync finishes (optional).

Check the result

Review the ahead/behind counts and the result shown after the operation finishes.

Next step: If Git reports conflicts, open the conflict guide.

Need another approach?Find a fix →