Please make use of the search feature, since this submission adds no further value over the exact same link submitted 6 days ago: https://news.ycombinator.com/item?id=36665189

Pedantically, it also wasn't a "stale pipeline," as one can read in their own description:

> Terraform itself protects against applying a stale plan, but in this case we are creating a fresh plan + apply after each merge. The problem is not a stale plan, but rather performing a plan + apply a non-current commit.