Git workflows ill-suited for non-CI/CD delivery models

7/10 High

Git works well for single-product CI/CD with a continuous main branch, but fails for delivery models common in pharma and statistical programming where multiple non-continuous deliveries sharing code are required. Classical Git workflows cannot be easily adapted.

GitCI/CD
Category
architecture
Workaround
none
Stage
deploy
Freshness
persistent
Scope
cross_platform
Recurring
No
Buyer Type
enterprise

Sources

Collection History

Query: “What are the most common pain points with Git for developers in 2025?”4/5/2026

Git works really well in a classical CI/CD setting where you have a single product that you want to have a continuous production version of (i.e. main branch)... This simply isn't how we deliver statistical programming products in pharma and hence classical git workflows cannot be easily used by us.

Created: 4/5/2026Updated: 4/5/2026