/add-repo

Add Repository

Add a new repository to Zapat's monitoring list.

Locate Zapat

First, find the Zapat installation:

if [ -n "$ZAPAT_HOME" ] && [ -d "$ZAPAT_HOME" ]; then
  echo "FOUND:$ZAPAT_HOME"
elif [ -d "$HOME/.zapat" ]; then
  echo "FOUND:$HOME/.zapat"
elif [ -f "./bin/zapat" ] && [ -f "./package.json" ] && grep -q '"name": "zapat"' ./package.json 2>/dev/null; then
  echo "FOUND:$(pwd)"
else
  echo "NOT_FOUND"
fi

If NOT_FOUND, tell the user: "Zapat isn't installed yet. Run /zapat:setup first to set it up."

Set ZAPAT_HOME to the found path. All paths below are relative to $ZAPAT_HOME.

Steps

1. Ask the user for:

   • GitHub path: owner/repo (e.g., acme-corp/new-service)
   • Local path: where the repo is cloned locally (e.g., /home/you/code/new-service)
   • Type: backend, web, ios, mobile, extension, marketing, or other

2. Validate the local path exists:

   ls -d <local_path>
   

   If it does not exist, ask if they want to clone it:

   gh repo clone <owner/repo> <local_path>
   

3. Check that the repo is not already in $ZAPAT_HOME/config/repos.conf. If it is, inform the user and ask if they want to update the existing entry.

4. Append the new entry to $ZAPAT_HOME/config/repos.conf:

   owner/repo	/path/to/local/clone	type
   

5. Ask: "Set up pipeline labels on this repo? (recommended for first-time repos)" If yes, run:

   $ZAPAT_HOME/bin/setup-labels.sh
   

   This creates the required labels (agent, agent-work, agent-research, hold, human-only, and internal status labels) on the repo.

6. Confirm:

   Added acme-corp/new-service to Zapat.
   The pipeline will pick it up on the next poll cycle (within 2 minutes).