Reenable main tests on Crowdin PRs#6076
Conversation
|
@decidim/core can you review this PR? |
|
Hi @mrcasals thanks for the PR! Just now I've been working on this. I was thinking to protocolize always building js bundles before merging Crowdin PRs. So what do we prefer to have tests for Crowdin PRs or @decidim/core manually build the JS bundles before merging them? |
|
But this already happened before 🤔 Bundles only need to be remade in these cases:
I think simply adding the tests for the Crowdin PRs will detect those changes while keeping the CI builds queue clean. The alternative is to set Crowdin to 24h no matter what, reenable CI builds for those PRs and force sync before releasing new versions. |
I don't really have any thoughts regarding this.
I'm ok with that. The only case where I think we may need translations before 24h is when we're making a release and on those cases we could sync manually. |
|
I've configured Crowdin to synchronize every 24h. |
* feature/initiatives_search_fo_new_design: Updates changelog Harmonizes the design of initiatives search in FO New question type "Matrix" in questionnaires (decidim#5948) Add filter options to Timeline and Activity tabs (decidim#5845) Remove relations between user and spaces on destroy account command (decidim#6041) Explain how to initialize a custom oauth2 client provider (decidim#6055) Reenable main tests on Crowdin PRs (decidim#6076) Enum and readonly component settings (decidim#6001) New Crowdin translations (decidim#6066) Add missing notifications (decidim#5906)
🎩 What? Why?
This PR re-enables the main CI builds (and only those) for Crowdin PRs, so that we can detect problems with the JS bundles.
Currently
developsdeems to be failing because of this.📌 Related Issues
📋 Subtasks
None