Actions
Bug #3338
closedcheckGenericFileContent 2.1 and 3.0 have desynchronized code between metadata and promises, leading to inconsistencies or uncorrected bugs
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
For some reasons, some merge between branches 2.3 and 2.4 when astray for checkGenericFileContent, resulting in :
- For version 3, the fix for #3069 isn't applied (the directive needs content to add), and was directed to 2.1 (which is wrong)
- The promises for version 3 include the possibility to not force the creation of file (#2945), which should be applied on 3.1 (the metadata doesn't include this modification)
Others versions seems to be correct
We have to resynchronise manually these files
Actions