.PHONY: all bootstrap setup check test lint lint-fix fmt fmt-check build clean deps test-coverage local install release release-snapshot docker hooks

# Version number
VERSION := 1.0.0-rc.1

# Build variables
GIT_REVISION := $(shell git rev-parse HEAD 2>/dev/null || echo "unknown")
GIT_COMMIT_DATE := $(shell git show -s --format=%cs HEAD 2>/dev/null || echo "unknown")

# Linker flags
LDFLAGS := -X 'sneak.berlin/go/vaultik/internal/globals.Version=$(VERSION)' \
           -X 'sneak.berlin/go/vaultik/internal/globals.Commit=$(GIT_REVISION)' \
           -X 'sneak.berlin/go/vaultik/internal/globals.CommitDate=$(GIT_COMMIT_DATE)'

# Default target
all: vaultik

# Install all development dependencies.
bootstrap:
	@script/bootstrap

# Prepare a fresh clone: bootstrap plus pre-commit hook.
setup:
	@script/setup

# Combined pre-commit/CI gate: tests, lint, format check.
check:
	@script/check

# Run tests only. This runs the ENTIRE suite -- there is no separate
# integration target and no build-tagged subset held back. In
# particular internal/vaultik/integration_test.go, which does full
# chunk -> pack -> encrypt -> upload -> restore round-trips, runs here.
# A `test-integration` target used to exist and was removed: no file in
# the repo carried a build tag, so `-tags=integration` selected nothing
# extra and the target was an exact duplicate of this one.
test:
	@script/test

# Check if code is formatted (read-only).
fmt-check:
	@script/fmt-check

# Format code.
fmt:
	@script/fmt

# Run linter only.
lint:
	@script/lint

# Apply the linter's autofixes (rewrites files).
lint-fix:
	@script/lint-fix

# Build binary.
vaultik: internal/*/*.go cmd/vaultik/*.go
	go build -ldflags "$(LDFLAGS)" -o $@ ./cmd/vaultik

# Clean build artifacts.
clean:
	rm -f vaultik
	go clean

# Install dependencies. The linter is deliberately not installed here:
# script/lint runs the digest-pinned golangci-lint image declared by the
# Dockerfile's lint stage, which is the single source of truth for the
# linter version. A second, separately pinned copy on PATH could drift
# from it and make a local `make lint` disagree with CI.
deps:
	go mod download

# Run tests with coverage. -count=1 for the same reason script/test
# uses it: without it an unchanged package is served from Go's test
# result cache, and a coverage profile assembled from cached results
# describes a run that did not happen.
test-coverage:
	go test -v -count=1 -coverprofile=coverage.out ./...
	go tool cover -html=coverage.out -o coverage.html

local:
	VAULTIK_CONFIG=$(HOME)/etc/vaultik/config.yml ./vaultik snapshot --debug list 2>&1
	VAULTIK_CONFIG=$(HOME)/etc/vaultik/config.yml ./vaultik snapshot --debug create 2>&1

install: vaultik
	cp ./vaultik $(HOME)/bin/

# Build and publish release artifacts (linux/darwin × amd64/arm64) via goreleaser.
release:
	goreleaser release --clean

# Dry-run a release build without publishing or tagging.
release-snapshot:
	goreleaser release --clean --snapshot

# Build Docker image.
docker:
	@script/docker

# Install pre-commit hook.
hooks:
	@script/install-precommit
