Conversation
Author
|
Updated the entry to release 1.0.1.0, which replaces 1.0.0.0: the cleaned file is now stored as a new file for the review copy, so the author's original upload is never modified. The entry also carries |
edersotto
force-pushed
the
blindReviewGuard-1.0.0.0
branch
from
September 15, 2026 18:18
59d2ee3 to
ad51d60
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Blind Review Guard 1.0.2.0, a generic plugin that checks the files a reviewer is about to receive for anything that identifies the authors, and can remove the identifying metadata. This update replaces the 1.0.0.0 entry.
What it does
How it plugs in
Core hooks only —
SubmissionFile::addandReviewAssignment::add— with files stored through the core file service andRepo::submissionFile(). The hooks are registered unconditionally and each callback checks whether the plugin is enabled in the submission's journal, following pkp/pkp-lib#11793, so files created from the command line or a queued job are covered. Settings use the standard plugin settings form with POST and CSRF validation; at site level there is nothing to configure.Tests
PKPTestCase(75: matching rules, cleaning that never writes the source, PDF and OOXML size limits, plugin classes against the installed PKP, site level, 38 locales).pkp/pkp-github-actionson OJS 3.5 (PHP 8.2/8.3, MySQL/PostgreSQL) — green; with a prepared submission it also sends a file to review and checks that the author's upload keeps its stored file.Checks run before updating this
xmllint --schema ./plugins.xsd ./plugins.xml --noout— validates.1.0.2.0:fc10d13275b3b1cc8ab305ecffaf3ffdUse of generative AI
Generative AI (Claude, by Anthropic) was used to write and run tests, improve the code and bring it in line with PKP standards. Every change was reviewed and tested by OJSBR, which maintains the plugin and is responsible for its releases.
GPL-3.0 · https://github.com/OJSBR/blindReviewGuard