Hi,
we are using StaticCMS with Astro site hosted on gitlab where we setup circleci CI site rebuild and deploy to our www server. This all works fine until we make and publish several changes made across different collections which trigger multiple commits to gitlab resulting in multiple ci pipelines building and publishing the site. There might be a race condition when a newer deployment would be overwritten by an older one in cases when an older CI job building the site finishes last.
To prevent this, would you consider a new feature which would batch cms changes to one commit so that all changes are published at once instead of in multiple commits?
Hi, we are using StaticCMS with Astro site hosted on gitlab where we setup circleci CI site rebuild and deploy to our www server. This all works fine until we make and publish several changes made across different collections which trigger multiple commits to gitlab resulting in multiple ci pipelines building and publishing the site. There might be a race condition when a newer deployment would be overwritten by an older one in cases when an older CI job building the site finishes last.
To prevent this, would you consider a new feature which would batch cms changes to one commit so that all changes are published at once instead of in multiple commits?
Thanks, Libor