Configuration

Configure LoveAutomate workflows, agent behavior, and integrations for your project.

Customize LoveAutomate to match your team's workflow and technology stack.

Project Settings

Configure these in your LoveAutomate dashboard under Project → Settings:

Setting	Description	Default
Default Branch	Branch to compare PRs against	`main`
Agent Mode	Thoroughness of AI analysis	`standard`
Auto-Heal	Automatically fix broken locators	`enabled`
Notifications	Where to send alerts	Dashboard

Workflow Configuration

Define workflows in your project settings or via YAML:

workflows:
  - name: PR Quality Gate
    trigger: pull_request
    agent:
      mode: adaptive
      focus: changed_files
      timeout: 300
    quality_gate:
      min_score: 70
      block_on_regression: true
    reporting:
      github_status: true
      pr_comment: true

  - name: Nightly Regression
    trigger: schedule
    schedule: "0 2 * * *"
    agent:
      mode: deep
      focus: full_application
    reporting:
      slack: "#qa-channel"
      email: team

Agent Configuration

Mode Options

Mode	Speed	Coverage	Best For
`shallow`	Fast	Changed files only	Quick PR checks
`standard`	Moderate	Changed + affected	Default workflows
`adaptive`	Varies	AI-determined scope	Smart resource use
`deep`	Thorough	Full application	Nightly regressions

Focus Options

changed_files — Only test what changed
affected_routes — Test routes impacted by changes
full_application — Complete test coverage
critical_paths — Focus on high-risk user flows

Integration Settings

CI/CD

LoveAutomate supports:

GitHub Actions
GitLab CI/CD
Jenkins
CircleCI
Bitbucket Pipelines

Notifications

Slack — Channel notifications for test results
Email — Summary reports to team members
Webhooks — Custom HTTP callbacks for automation

Issue Tracking

Link test failures to your issue tracker:

GitHub Issues
Jira
Linear
Asana (coming soon)

Environment Variables

Set these in your CI pipeline:

LOVEAUTOMATE_API_KEY=la_your_api_key
LOVEAUTOMATE_PROJECT_ID=proj_abc123
LOVEAUTOMATE_ENVIRONMENT=staging

Best Practices

Start with adaptive mode — Let the AI decide the right scope
Set quality gates on PRs — Block merges when regressions are detected
Run nightly deep scans — Catch issues that PR checks might miss
Enable auto-healing — Reduce maintenance burden automatically
Configure Slack alerts — Keep your team informed in real-time