## Migrate `gmail_mcp.py` config from GitHub to self-hosted Gitea
Part of parent: #18 ([brencher] Migrate remaining configs from GitHub to self-hosted Gitea).
### Current state
`admin/brencher/backend/configs/gmail_mcp.py`:
```python
clone = GitClone(url="https://github.com/rudolf1/uber_backup.git", branchNamePrefix="immoscout")
```
### Target state
Adopt the multi-remote pattern already used in `brencher.py` and `brencher2.py`:
```python
clone = GitClone(remotes=[
{"name": "github", "url": "https://github.com/rudolf1/uber_backup.git"},
{"name": "gitea_admin", "url": "https://gitea.rudolf.keenetic.link/admin/brencher"},
{"name": "gitea_hermes", "url": "https://gitea.rudolf.keenetic.link/hermes/brencher"},
], branchNamePrefix="immoscout")
```
(Keep `branchNamePrefix="immoscout"` exactly as it is today.)
### Acceptance criteria
- `gmail_mcp.py` uses `GitClone(remotes=[...])` with the three remotes above.
- No behavior change for `stack_name="gmail_mcp"` (downstream of `clone`).
- Single-purpose PR in `admin/brencher` referencing this issue.
- Closes #18 sub-task when merged.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Migrate
gmail_mcp.pyconfig from GitHub to self-hosted GiteaPart of parent: #18 ([brencher] Migrate remaining configs from GitHub to self-hosted Gitea).
Current state
admin/brencher/backend/configs/gmail_mcp.py:Target state
Adopt the multi-remote pattern already used in
brencher.pyandbrencher2.py:(Keep
branchNamePrefix="immoscout"exactly as it is today.)Acceptance criteria
gmail_mcp.pyusesGitClone(remotes=[...])with the three remotes above.stack_name="gmail_mcp"(downstream ofclone).admin/brencherreferencing this issue.Linked to parent #18. Related work: #19, #20, #21, #22.