# Example configuration for git-auto-tracker.
# Deployment-specific values can be overridden with environment variables
# using the convention GIT_AUTO_TRACKER_<SECTION>__<KEY>, e.g.
#   GIT_AUTO_TRACKER_REPOSITORY__PATH=D:/SCADA/Project

application:
  timezone: Europe/Stockholm

repository:
  path: "D:/SCADA/Project"
  branch: main

git:
  user_name: "SCADA Change Tracker"
  user_email: "git-auto-tracker@localhost"

files:
  include:
    - "**/*"

  exclude:
    - "**/*.tmp"
    - "**/*.log"
    - ".git/**"
    # When content extraction (Section 45) is enabled, exclude the raw
    # binary databases so the repository tracks the readable artifacts
    # instead of opaque blobs:
    # - "**/*.sqlite"

security:
  forbidden_patterns:
    - "**/*.key"
    - "**/*.pem"
    - "**/secrets.*"
    - "**/credentials.*"

author_resolution:
  resolvers:
    - sidecar_metadata
  minimum_confidence: probable
  fallback: unknown

commit:
  # Separator between the parts of a one-line file entry in commit
  # messages (Section 15). Must not occur inside paths, author
  # identifiers or timestamps.
  file_separator: ";"

# Derived artifacts (Section 45): extracts configured SQLite databases
# into plain-text artifacts that are tracked like any other file. One
# sub-folder per source database (named after the database file), one
# JSON Lines file per table, under a configurable output root inside
# the repository. Extraction opens the source read-only via a snapshot
# copy; artifacts are byte-stable so unchanged content produces no
# commit; a table removed from the database removes its artifact.
extraction:
  enabled: true
  output_root: "extracted"
  format: "jsonl"
  sources:
    - path: "data/VV_FALKENBERG.signals.db"
      # tables:                # optional; default: all user tables
      #   - "alarms"
      #   - "events"

logging:
  level: INFO
  console: true
  file: "../logs/git-auto-tracker.log"
  max_size_mb: 20
  backup_count: 10