Change Details

**Motivation** The AbuseFilter is an extension that checks if files should be uploaded to Commons or if they don't fulfil the project's criteria. One such rule is for example the "0-Byte-Rule", that disallows files where the file page is empty. While this makes perfect sense for the most recent revision, since the FileImporter moves many revisions it would be great if rules in the AbuseFilter could be written in such a way, that it is clear if this rule should apply to all revisions of a file or only the most recent one. **Acceptance Criteria** [] Investigate whether it will be possible to provide a way that rules of the AbuseFilter extension can include that they should only be carried out for the most recent revision [] Discuss idea with AbuseFilter extension maintainers **Notes** - It might be specifically from FileImporter for FileImporter, but even better (if same effort applies): - It might be totally independent from, but also applicable for the FileImporter, talking about “this should happen on old revisions, no matter where it was imported from” **Storypoints** 5

**Motivation** The AbuseFilter is an extension that checks if files should be uploaded to Commons or if they don't fulfil the project's criteria. One such rule is for example the "0-Byte-Rule", that disallows files where the file page is empty. While this makes perfect sense for the most recent revision, since the FileImporter moves many revisions it would be great if rules in the AbuseFilter could be written in such a way, that it is clear if this rule should apply to all revisions of a file or only the most recent one. **Acceptance Criteria** [] Investigate whether it will be possible to provide a way that rules of the AbuseFilter extension can include that they should only be carried out for the most recent revision [] Discuss idea with AbuseFilter extension maintainers **Notes** - It might be specifically from FileImporter for FileImporter, but even better (if same effort applies): - It might be totally independent from, but also applicable for the FileImporter, talking about “this should happen on old revisions, no matter where it was imported from”

**Motivation** The AbuseFilter is an extension that checks if files should be uploaded to Commons or if they don't fulfil the project's criteria. One such rule is for example the "0-Byte-Rule", that disallows files where the file page is empty. While this makes perfect sense for the most recent revision, since the FileImporter moves many revisions it would be great if rules in the AbuseFilter could be written in such a way, that it is clear if this rule should apply to all revisions of a file or only the most recent one. **Acceptance Criteria** [] Investigate whether it will be possible to provide a way that rules of the AbuseFilter extension can include that they should only be carried out for the most recent revision [] Discuss idea with AbuseFilter extension maintainers **Notes** - It might be specifically from FileImporter for FileImporter, but even better (if same effort applies): - It might be totally independent from, but also applicable for the FileImporter, talking about “this should happen on old revisions, no matter where it was imported from” **Storypoints** 5