Qodo Pr Resolver

# Gerrit Provider Reference

Gerrit uses **Changes** (not Pull Requests). All API interactions use `curl` + HTTP Basic Auth — there is no official Gerrit CLI.

**Key differences from other providers:**
- Changes are identified by a `Change-Id` in the commit message (not a branch name)
- Push for review: `git push origin HEAD:refs/for/<target-branch>` (not `git push`)
- All comment operations go through a **single unified endpoint** (`POST /revisions/current/review`)
- Qodo posts as **tagged human comments** with `tag: "autogenerated:qodo"` (not robot comments)
- All API responses are prefixed with `)]}'` — must strip before JSON parsing

## Provider Detection

Gerrit detection is multi-signal (checked after GitHub/GitLab/Bitbucket/Azure DevOps):

1. **`.gitreview` file** in repo root (strongest signal) — parse `host` and `project` from it
2. **Port `29418`** in SSH remote URL
3. **`googlesource.com`** in remote URL (Google-hosted Gerrit)

```bash
# Check for .gitreview file
if [ -f .gitreview ]; then
  GERRIT_HOST=$(git config -f .gitreview gerrit.host 2>/dev/null)
  GERRIT_PROJECT=$(git config -f .gitreview gerrit.project 2>/dev/null)
fi

# Check remote URL patterns
REMOTE_URL=$(git remote get-url origin)
echo "$REMOTE_URL" | grep -qE ':29418/' && echo "Gerrit (SSH)"
echo "$REMOTE_URL" | grep -q 'googlesource.com' && echo "Gerrit (Google)"
```

## Prerequisites

### Authentication

HTTP Basic Auth with a password generated from Gerrit's settings page.

**Qodo config** (`~/.qodo/config.json`) — store credentials persistently:
```json
{
  "GERRIT_URL": "https://review.example.com",
  "GERRIT_USERNAME": "your-username",
  "GERRIT_HTTP_PASSWORD": "your-http-password"
}
```
- `GERRIT_URL`: Gerrit instance base URL (always required — there is no default host)
- `GERRIT_USERNAME`: Your Gerrit username
- `GERRIT_HTTP_PASSWORD`: HTTP password from **Settings → HTTP Credentials** (this is NOT your account password)

### Extract project info from `.gitreview`

```bash
GERRIT_PROJECT=$(git config -f .gitreview gerrit.project 2>/dev/null)
TARGET_BRANCH=$(git config -f .gitreview gerrit.defaultbranch 2>/dev/null || echo "main")
```

### Magic JSON prefix

All Gerrit REST API responses start with `)]}'` on the first line (XSS protection). Strip it before parsing:
```bash
| tail -c +6 | python3 -m json.tool
```

Every `curl` command in this file includes this pipe.

### Verify

```bash
curl -s -u "$GERRIT_USERNAME:$GERRIT_HTTP_PASSWORD" \
  "$GERRIT_URL/a/accounts/self" | tail -c +6 | python3 -m json.tool
```

**Note:** All authenticated endpoints use the `/a/` prefix in the path. Some Gerrit instances also have an API prefix (e.g. `/r/`) — if `GERRIT_URL` includes it (e.g. `https://git-master.example.com/r`), the full path becomes `/r/a/changes/...`.

## Find Open Change

Gerrit has no "source branch" concept. Changes are identified by `Change-Id` from the commit message.

### Extract Change-Id from commit

```bash
CHANGE_ID=$(git log -1 --format=%b | grep 'Change-Id:' | sed 's/.*Change-Id: //')
```

### Query by Change-Id (preferred)

```bash
curl -s -u "$GERRIT_USERNAME:$GERRIT_HTTP_PASSWORD" \
  "$GERRIT_URL/a/changes/?q=change:$CHANGE_ID+status:open&o=CURRENT_REVISION&o=MESSAGES" \
  | tail -c +6 | python3 -m json.tool
```

### Query by project + owner (fallback)

```bash
curl -s -u "$GERRIT_USERNAME:$GERRIT_HTTP_PASSWORD" \
  "$GERRIT_URL/a/changes/?q=status:open+project:$GERRIT_PROJECT+owner:self&o=CURRENT_REVISION" \
  | tail -c +6 | python3 -m json.tool
```

Response is a JSON array. Key fields: `_number` (change number), `project`, `branch`, `current_revision`.

## Fetch Review Comments

Gerrit has **three separate comment endpoints**. Fetch all three.

### Human comments (where Qodo posts)

Qodo posts inline comments as **human comments** with `tag: "autogenerated:qodo"`. This is the primary endpoint to check.

Filter for Qodo: check `tag` field equals `"autogenerated:qodo"`, or `author.username` matches the Qodo bot user (e.g. `"