Does Apps Script need CI/CD? — What happens after your scripts multiply.

One Apps Script project is easy. Ten scattered across an org is a mess. Here's how consistent constraints — not more features — solve the problem. You can't escape Google Sheets No engineer wakes up excited to open the Apps Script editor. But in an organization, leaving Google Sheets behind isn't really an option. Finance manages budgets in spreadsheets. Legal tracks contracts in spreadsheets. Sales updates their pipeline in spreadsheets. No matter how many modern tools engineering introduces, everyone else lives in Google Sheets. And Google Apps Script is the automation layer that naturally grows on top of that. "Just migrate to Node.js." "Rewrite it in Python." Technically, sure. But the data lives in spreadsheets and the stakeholders read spreadsheets. Apps Script is the rational choice. The problem isn't choosing Apps Script. It's that the moment you choose it, you tend to abandon software engineering practices. Scripts multiply Apps Script projects start small. A form response tri