Pull your branch

ComputerWeb app3 min readUpdated October 4, 2026

Bring new commits from your branch's online copy, such as a GitHub repository, onto your computer from the branch menu. Enjoy shows what came in, or explains what went wrong.

Before you start

  • Your project is connected to an online copy, such as a GitHub repository, and Git on your computer can sign in to it. If it isn’t set up yet, ask your agent to set it up.
  • Your branch follows a branch in the online copy. A branch you’ve pushed before usually does.
  • No agent is working in your project’s main folder. Pulling changes your project’s files, so it waits until that work finishes.

Steps

  1. Open the branch menu

    At the bottom of the message box, select the button with the branch icon.

  2. Select Pull

    It’s beside the current branch, the one with the check mark, next to Push. The button changes to Pulling….

    The branch menu open. The current branch has a check mark, then Pull and Push side by side. Highlighted: Pull.The branch menu open. The current branch has a check mark, then Pull and Push side by side. Highlighted: Pull.
  3. Read the result

    It appears under the branch, with your branch’s name:

    • Pulled 2 commits into main. Your project’s files now include those commits.
    • Already up to date. There was nothing new to bring in.
    • Couldn’t pull main. Select Git details to read Git’s own message, then see below.
    The branch menu after a pull, with "Pulled 2 commits into main." under the current branch. Highlighted: The pull result.The branch menu after a pull, with "Pulled 2 commits into main." under the current branch. Highlighted: The pull result.

Good to know

  • Pull is for the branch your project’s main folder is on. To pull another branch, switch to it first. A worktree’s branch doesn’t have Pull, so ask the worktree’s agent to pull it.
  • Enjoy only moves your branch forward to the online copy’s newer commits. It never merges, rebases, or sets your changes aside, so a pull either finishes or leaves your files as they were.
  • Uncommitted changes stay as they are, unless the new commits change the same files. Then Git stops before changing anything.
  • While an agent works in the main folder, Pull isn’t available and the menu shows Work in progress. You can still push.
  • The result stays until you open the menu again or switch branches.
  • Pull works the same in the web app. In a project someone shared with you, you need Can work access. The iPhone app can’t pull.

If something goes wrong

Both copies have new commits

If Git details say “Not possible to fast-forward,” your computer and the online copy each have commits the other doesn’t. Enjoy doesn’t combine them for you. Ask your agent: “Pull the online changes into this branch and merge them.”

Uncommitted changes are in the way

If Git details say your local changes would be overwritten, commit them first, then select Pull again. See Save your changes with a commit.

The branch doesn’t follow an online branch

If Git details say there is no tracking information for the current branch, Git doesn’t know which online branch to pull from. Ask your agent: “Set this branch’s upstream.” After that, Pull works for this branch.

Git can’t sign in

Enjoy can’t answer Git’s password prompts. If the details mention a username, password, or permission, set up Git so it can sign in without asking, or ask your agent to help.

Other messages

  • “Git took too long. Try again.” Enjoy stops waiting for Git after 30 seconds. Check your internet connection, then select Pull again.
  • “Stop active work in this project to pull.” Wait for agents working in the main folder to finish.
  • “The active branch changed. Reopen the branch menu and try again.”
  • “Wait for the branch change to finish.”, “Wait for the pull to finish.”, or “Wait for the push to finish.” Wait a moment, then try again.
  • “Update the desktop app to pull branches.” Update Enjoy on your computer.
Did this help?

Still need a hand?

Email help@enjoy.dev with your computer, your Enjoy version, and what happened. Leave out passwords and sign-in codes. For questions and ideas, join our Slack community .