sync-arch-memory

Sync architectural memory repositories by running the script to pull or clone Git repositories from Azure DevOps into a local cache. It uses commit hashes to detect staleness, fetching updates only when remote changes are detected.

The Git commit hash mechanism compares local and remote repository states to detect staleness. If the hashes differ, it performs a pull or clone to update the local cache, avoiding unnecessary Git operations when repositories are already current.

Yes, you can override the default cache location and individual repository paths using environment variables. This allows flexible configuration of where architectural memory repositories are stored locally during the Git sync process.

Yes, Azure CLI is required for authentication when syncing repositories from Azure DevOps. The script integrates with Azure CLI to handle credentials, enabling Git to pull and clone architectural memory repositories securely.

Run the sync script to pull the latest architectural memory repositories from Azure DevOps. This ensures all team members have current guidelines for Go, Bash, Terraform, and other domains stored in their local cache.

The sync skips Git pull operations when local and remote commit hashes match, indicating the local cache is already current. This staleness detection mechanism avoids redundant data transfers and speeds up the synchronization process.