Workflow

Daily team workflow

This is the normal rhythm when working with a team:

# Morning: get the latest from the team
ag fetch

# Work on your tasks (edit files all day)

# Before lunch: save your progress
ag save "Working on the dashboard"

# After lunch: save and share
ag save "Finished the dashboard layout"
ag upload

# End of day: make sure everything is shared
ag info          # Check your status
ag upload        # Upload if you have unsaved work

First time joining a project

When you’re new to a project:

# 1. Download the project (do this once)
ag fetch https://github.com/team/project.git

# 2. Check the dashboard to see what's happening
ag info

# 3. Start working!

Handling merge conflicts

Sometimes your changes and the team’s changes clash. Here’s what to do:

When it happens

You run ag fetch and see:

[WARN] Conflicts detected:
    • index.html
    • style.css

Step-by-step resolution

Open the listed files in your editor

Look for conflict markers

<<<<<<< HEAD
Your version of the code
=======
Their version of the code
>>>>>>>

<<<<<<< HEAD = your changes
======= = divider between versions
>>>>>>> = their changes

Edit the file to keep what you want

You can:

Keep your version (delete the markers and their version)
Keep their version (delete the markers and your version)
Mix both versions together manually

Remove all the conflict markers (<<<<<<<, =======, >>>>>>>)

Save the file in your editor

Tell Anchor4Git you're done

ag save

This step is important as if you do not do this; upload will be blocked.

Share your resolution

ag upload

Example: Resolving a conflict

Before (conflicted file):

<<<<<<< HEAD
Welcome to our site
=======
Welcome to our website!
>>>>>>>

After (resolved):

Welcome to our website!

Then save and upload as normal.

Going back to an old version

Look at an old version (temporary)

# See what the project looked like at an earlier save
ag goto abc1234

# Look around... then press Enter in the terminal to return

Roll back to an old version (permanent)

# Find the save you want to go back to
ag info

# Permanently go back
ag goto abc1234 --reset

Stay on an old version

# Go to old version and stay there
ag goto abc1234 --stay

# When you want to come back
ag goto HEAD

To find the save ID, run ag info

Setting up a shared project from scratch

If you’re the team lead starting a new project:

# 1. Create a shared repository on GitHub, GitLab, etc.
#    (this step depends on your git repository provider)

# 2. Create the project locally
mkdir my-project
cd my-project
ag init "My Project"

# 3. Fetch it locally to sync details
ag fetch https://github.com/team/my-project.git

# 4. Save the initial setup
ag save "Initial project setup"

# 5. Upload the project
ag upload

# 6. Tell your team to run:
#    ag fetch https://github.com/team/my-project.git

You’ll need to set up authentication (like a personal access token) for GitHub/GitLab. Check their documentation for help.
Anchor4Git automatically handles login to major providers like GitHub using a UI.

Quick reference

Situation	Command
First time setup	`ag fetch <url>`
Daily download	`ag fetch`
Save progress	`ag save "what I did"`
Share with team	`ag upload`
Check status	`ag info`
Look at old version	`ag goto <id>`
Return to latest	`ag goto HEAD`
Change settings	`ag config`

Getting Started

Commands

Daily team workflow

First time joining a project

Handling merge conflicts

When it happens

Step-by-step resolution

Example: Resolving a conflict

Going back to an old version

Look at an old version (temporary)

Roll back to an old version (permanent)

Stay on an old version

Setting up a shared project from scratch

Quick reference

​Daily team workflow

​First time joining a project

​Handling merge conflicts

​When it happens

​Step-by-step resolution

​Example: Resolving a conflict

​Going back to an old version

​Look at an old version (temporary)

​Roll back to an old version (permanent)

​Stay on an old version

​Setting up a shared project from scratch

​Quick reference

Daily team workflow

First time joining a project

Handling merge conflicts

When it happens

Step-by-step resolution

Example: Resolving a conflict

Going back to an old version

Look at an old version (temporary)

Roll back to an old version (permanent)

Stay on an old version

Setting up a shared project from scratch

Quick reference