You want to prevent concurrent deployments to production but not cancel in-progress deployments when a new one queues. Which concurrency configuration achieves this?

Setting 'concurrency: group: production' with 'cancel-in-progress: false' creates a queue — only one deployment runs at a time, but in-progress deployments are not cancelled when a new one arrives. The new run waits until the current one completes. This is the correct pattern for deployment pipelines where you don't want to interrupt a partially completed deployment. 'cancel-in-progress: true' would abort an ongoing deployment when a new push arrives — dangerous for production deployments. Using 'github.run_id' as the group key creates a unique group per run, which means no concurrency control at all.