@claude we need to prevent the app from pulling a change if a pull is already in progress. If a pull is already in progress further pulls should be queued and run after the current pull is finished and any deployment script that has been called has finished running.

[simonjcarr]

[claude]

Claude finished @simonjcarr's task —— View job • claude/issue-3-20250923-2148 • Create PR ➔

---

✅ Completed: Pull queue implementation to prevent concurrent pulls

I've successfully implemented a queue mechanism to prevent concurrent pull operations in SPDeploy.

Changes Made:

1. Created pull_queue.go - A thread-safe queue system that:

   • Uses mutex-based synchronization to prevent race conditions
   • Queues pull requests when one is already in progress
   • Prevents duplicate pull requests for the same repository/branch
   • Processes queued items sequentially after current operations complete

2. Modified monitor_v2.go to:

   • Initialize the pull queue when creating the monitor
   • Queue pull requests instead of executing them directly
   • Process the queue in a separate goroutine
   • Track completion of both git pull and deployment scripts

3. Added pull_queue_test.go with comprehensive tests for:

   • Queue operations (add, get, size)
   • Duplicate prevention
   • Processing state management
   • Blocking behavior when processing is active

Key Features:

• ✅ Prevents concurrent pull operations
• ✅ Queues subsequent pull requests
• ✅ Waits for deployment scripts to complete before processing next item
• ✅ Thread-safe implementation using mutex and condition variables
• ✅ Prevents duplicate requests in the queue
• ✅ Logs queue status for monitoring

|