git provider doc refinement, rust lints

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: untra

docs/getting-started/git/github.md

@@ -2,6 +2,7 @@
 title: "GitHub"
 description: "Configure GitHub integration with Operator."
 layout: doc
+published: true
 ---
 
 # GitHub
@@ -19,7 +20,7 @@ Connect Operator to GitHub for repository management and pull requests.
 
 ## Install GitHub CLI
 
-The `gh` CLI handles authentication and API operations.
+The `gh` CLI handles authentication and API operations. Operator uses `gh` directly rather than raw API calls.
 
 ### macOS
 
@@ -35,6 +36,9 @@ curl -fsSL https://cli.github.com/packages/githubcli-archive-keyring.gpg | sudo
 echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | sudo tee /etc/apt/sources.list.d/github-cli.list > /dev/null
 sudo apt update
 sudo apt install gh
+
+# Fedora/RHEL
+sudo dnf install gh
 ```
 
 ### Windows
@@ -43,20 +47,19 @@ sudo apt install gh
 winget install --id GitHub.cli
 ```
 
-### Authenticate
+## Authenticate
+
+The `gh` CLI manages authentication, including OAuth flows and credential storage:
 
 ```bash
 gh auth login
 ```
 
-Follow the prompts to authenticate via browser or token.
-
-## Create Personal Access Token
+Follow the prompts to authenticate via browser or token. Verify with:
 
-1. Go to GitHub Settings > Developer settings > Personal access tokens
-2. Click "Generate new token (classic)"
-3. Select scopes: `repo`, `workflow`
-4. Copy the token
+```bash
+gh auth status
+```
 
 ## Configuration
 
@@ -67,38 +70,32 @@ Add GitHub to your Operator configuration:
 
 [git.github]
 enabled = true
-token_env = "GITHUB_TOKEN"
-owner = "your-username"  # or organization
-repo = "your-repo"
+token_env = "GITHUB_TOKEN"   # env var for token (used as fallback if gh CLI auth is unavailable)
 ```
 
-Set your token:
+If `token_env` is set, export the token:
 
 ```bash
 export GITHUB_TOKEN="ghp_xxxxx"
 ```
 
-## Pull Request Settings
+### Provider Auto-Detection
 
-Configure PR behavior:
+Operator auto-detects GitHub from your git remote URL. You can also set it explicitly:
 
 ```toml
-[git.github.pr]
-base_branch = "main"
-draft = false
-auto_merge = false
-reviewers = ["teammate1", "teammate2"]
-labels = ["automated", "ai-generated"]
+[git]
+provider = "github"
 ```
 
-## Branch Naming
+### Shared Git Settings
 
-Configure branch name format:
+Branch naming and worktree settings live under the shared `[git]` section (see [Supported Git Repositories](/getting-started/git/) for details):
 
 ```toml
-[git.github]
-branch_format = "{type}/{ticket_id}-{slug}"
-# Example: feat/PROJ-123-add-login
+[git]
+branch_format = "{type}/{ticket_id}"
+use_worktrees = false
 ```
 
 ## Commit Messages
@@ -117,22 +114,20 @@ Ticket: PROJ-123
 
 ### Authentication errors
 
-Test your token:
+Check your auth status:
 
 ```bash
-curl -H "Authorization: token $GITHUB_TOKEN" \
-     https://api.github.com/user
+gh auth status
 ```
 
 ### Permission denied
 
-Ensure your token has `repo` scope and you have push access.
+Ensure you have push access to the repository and your `gh` session is authenticated.
 
 ### Rate limiting
 
-GitHub has API rate limits. Check remaining quota:
+Check remaining API quota:
 
 ```bash
-curl -H "Authorization: token $GITHUB_TOKEN" \
-     https://api.github.com/rate_limit
+gh api rate_limit
 ```

docs/getting-started/git/gitlab.md

@@ -1,78 +1,131 @@
 ---
 title: "GitLab"
-description: "Configure GitLab integration with Operator (Coming Soon)."
+description: "Configure GitLab integration with Operator."
 layout: doc
 published: true
 ---
 
 # GitLab
 
-GitLab integration is planned for a future release.
+Connect Operator to GitLab for repository management and merge requests.
 
-## Planned Features
+## Prerequisites
 
-When available, GitLab support will include:
+| Requirement | Purpose | Verification |
+|------------|---------|--------------|
+| `git` | Version control | `git --version` |
+| `glab` | GitLab CLI | `glab --version` |
+| GitLab account | Repository access | - |
+| Push access | Create branches/MRs | - |
 
-- Merge request creation and monitoring
-- Review status tracking
-- CI/CD pipeline status integration
-- Branch management
+## Install GitLab CLI
 
-## Expected Prerequisites
+The `glab` CLI handles authentication and API operations. Operator uses `glab` directly rather than raw API calls.
 
-GitLab integration will require:
+### macOS
 
-| Requirement | Purpose |
-|------------|---------|
-| GitLab account | Repository access |
-| Personal Access Token or Project Token | API authentication |
-| `glab` CLI (optional) | Alternative to direct API |
+```bash
+brew install glab
+```
 
-### Token Scopes (Planned)
+### Linux
 
-- `api` - Full API access
-- `read_repository` - Read repository contents
-- `write_repository` - Push changes
+```bash
+# Debian/Ubuntu
+curl -fsSL https://gitlab.com/gitlab-org/cli/-/releases/permalink/latest/downloads/glab_amd64.deb -o glab.deb
+sudo dpkg -i glab.deb
 
-## Planned Configuration
+# Fedora/RHEL
+sudo dnf install glab
+```
+
+### Windows
+
+```powershell
+winget install --id GLab.GLab
+```
+
+## Authenticate
+
+The `glab` CLI manages authentication, including OAuth flows and credential storage:
+
+```bash
+glab auth login
+```
+
+Follow the prompts to authenticate via browser or token. Verify with:
+
+```bash
+glab auth status
+```
+
+## Configuration
+
+Add GitLab to your Operator configuration:
 
 ```toml
 # ~/.config/operator/config.toml
 
-[git]
-provider = "gitlab"
-
 [git.gitlab]
 enabled = true
-token_env = "GITLAB_TOKEN"
-host = "gitlab.com"  # Or self-hosted instance
-project_id = "namespace/project"
+token_env = "GITLAB_TOKEN"       # env var for token (used as fallback if glab CLI auth is unavailable)
+host = "gitlab.com"              # or your self-hosted instance (e.g., "gitlab.example.com")
 ```
 
-### Merge Request Settings (Planned)
+If `token_env` is set, export the token:
 
-```toml
-[git.gitlab.mr]
-target_branch = "main"
-draft = false
-remove_source_branch = true
-squash = false
-reviewers = ["username1", "username2"]
-labels = ["automated", "ai-generated"]
+```bash
+export GITLAB_TOKEN="glpat-xxxxx"
 ```
 
-## CLI Alternative
+Merge request operations (create, monitor, review tracking) are not yet implemented. Provider detection, configuration, and `glab` CLI authentication work today.
 
-GitLab's official CLI (`glab`) may be used as an alternative:
+### Provider Auto-Detection
+
+Operator auto-detects GitLab from your git remote URL, including self-hosted instances (any URL containing `gitlab.`):
 
 ```bash
-# Install glab
-brew install glab
+# All of these are auto-detected as GitLab:
+git@gitlab.com:owner/repo.git
+https://gitlab.com/owner/repo
+https://gitlab.example.com/owner/repo
+```
 
-# Authenticate
-glab auth login
+You can also set the provider explicitly:
+
+```toml
+[git]
+provider = "gitlab"
 ```
 
-## Contributing
+### Shared Git Settings
+
+Branch naming and worktree settings live under the shared `[git]` section (see [Supported Git Repositories](/getting-started/git/) for details):
+
+```toml
+[git]
+branch_format = "{type}/{ticket_id}"
+use_worktrees = false
+```
 
-Interested in helping implement GitLab support? See the [Provider Support](/getting-started/git/provider-support/) guide for architecture details.
+## Troubleshooting
+
+### Authentication errors
+
+Check your auth status:
+
+```bash
+glab auth status
+```
+
+### Permission denied
+
+Ensure you have push access to the repository and your `glab` session is authenticated.
+
+### Self-hosted connectivity
+
+If using a self-hosted GitLab instance, verify the `host` value in your config matches the instance hostname and that the instance is reachable:
+
+```bash
+glab auth status --hostname gitlab.example.com
+```

docs/getting-started/git/index.md

@@ -6,7 +6,7 @@ layout: doc
 
 # Supported Git Repositories
 
-Operator integrates with Git hosting platforms to manage branches and pull requests.
+Operator integrates with Git hosting platforms to manage branches and pull/merge requests.
 
 ## Prerequisites
 
@@ -21,6 +21,30 @@ All providers require:
 | Platform | Status | CLI Tool | Notes |
 |----------|--------|----------|-------|
 | [GitHub](/getting-started/git/github/) | Supported | `gh` | Full PR integration |
+| [GitLab](/getting-started/git/gitlab/) | Partial | `glab` | Detection and config ready; MR operations planned |
+
+## Provider Auto-Detection
+
+Operator detects your Git provider from the remote URL automatically. You can override this in config:
+
+```toml
+[git]
+provider = "github"   # or "gitlab"
+```
+
+## Shared Git Configuration
+
+These settings apply regardless of provider:
+
+```toml
+[git]
+branch_format = "{type}/{ticket_id}"   # Branch naming pattern
+use_worktrees = false                   # Per-ticket worktree isolation
+```
+
+**Branch format variables:** `{type}` is the ticket type prefix (e.g., `feature`, `fix`, `spike`, `investigation`), `{ticket_id}` is the ticket identifier.
+
+**Worktrees:** When enabled, Operator creates isolated git worktrees per ticket, allowing parallel development without branch switching.
 
 ## How It Works
 
@@ -29,7 +53,7 @@ When an agent completes work on a ticket:
 1. **Branch**: Creates a feature branch from main
 2. **Commit**: Commits changes with ticket reference
 3. **Push**: Pushes branch to remote
-4. **PR**: Opens a pull request for review
+4. **PR/MR**: Opens a pull request or merge request for review
 
 ## Local Git