I'm not sure the concurrency key can solve the issue of old code after new code,... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

verdverm on Aug 19, 2021 | parent | context | favorite | on: Automating a Software Company with GitHub Actions

I'm not sure the concurrency key can solve the issue of old code after new code, in the general case.

What happens if there are conflicting migrations on two "parallel" branches?

What happens in you bad luck situation when commits are pushed in rapid succession on the same branch?

danpalmer on Aug 20, 2021 [–]

With the concurrency key at the top level, actions run it commit order.

As for running migrations on the same database from multiple branches, not a good idea. Probably best to decide on the branch that is the release branch (maybe main/master) and only deploy from that.

Consider applying for YC's Fall 2026 batch! Applications are open till July 27.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact