Read waiting work

Understand repository and worktree counts, preview commits, and choose the next action.

Start with the repository and branch

push& (Pushand) brings together the repositories you watch and their linked worktrees. A worktree is another working folder for the same repository, often on another branch. Several worktrees still count as one repository for your licence.

Check the repository, worktree and branch before taking an action. A local branch can also have waiting commits when it is not checked out in a working folder.

Read counts and previews

The waiting count measures commits to push, rather than changed files or repositories. A branch’s preview shows the waiting commit subjects and the files they change. Uncommitted changes are a separate state; they are not extra commits in that count.

Counts compare your local work with the last fetched state of its tracked remote branch. A refresh reads that known state; it is not a promise that nobody has changed the remote since. Push and pull check the remote again before acting, so a newer change can prevent an action that looked available.

Choose the next action

  • Ahead: local commits are waiting to be pushed. When the branch is not behind or diverged, push sends those commits to its existing tracked remote branch.
  • Behind: the tracked remote branch has commits you do not have locally. A fast-forward pull brings a clean, checked-out branch up to date without rewriting its history.
  • Diverged: both sides have different commits. Review and resolve the difference in Git before trying an ordinary push or pull.
  • Publish: a new branch has no tracked remote branch yet. Publishing creates one and asks for approval by default.

A branch without a working folder can be pushed, but must be checked out in Git before it can be pulled. A detached checkout has no ordinary branch action. These states do not mean that your work has been deleted.

Review a refusal before retrying

An action can be unavailable because of uncommitted changes, a changed remote, your safety settings, or view-only access. Read the error beside the affected work before retrying. Do not enable a more destructive action just to clear a refusal.

Use safety settings to understand the safeguards, or licence help if counts and previews work but Git actions are disabled.

Back to the Guide · Need a hand? Contact us