hlfan left a comment (openstreetmap/openstreetmap-website#6836)
Hence _can_ and _shouldn't_ and not _have to_ and _mustn't_.
I don't know the specifics of what git.osm.org can run in terms of CI, but some
indication of where in that multi-stage cycle we are would probably still help.
Emphasizing the _anytime_ part of the deploy approach, the order-of-operations
decision could include this consideration:
> Should I merge that pr now and then deploy, or deploy now and then merge?
If one way has an annotation with 17 pending translation migrations, and the
other does not, the path forward is clearer than when deciding between 15 or
18. It shouldn't be a deciding factor for emergency fixes.
I see the goal here not as to block all deploys with pending translation
migrations, just to reduce the number of deploys with unnecessary pending
translation migrations.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6836#issuecomment-3953274519
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/6836/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
