-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature request: review diffs #320
Comments
HotCRP already stores this information & has for years. Unfortunately, there are some conceptual roadblocks in showing it to users—especially to authors, who should not see most diffs (but should see some)—that have kept me from making it visible. Contributions welcome. |
On Sat, 9 Sept 2023 at 13:50, Eddie Kohler ***@***.***> wrote:
HotCRP already stores this information & has for years. Unfortunately,
there are some conceptual roadblocks in showing it to users—especially to
authors, who should not see most diffs (but should see some)—that have kept
me from making it visible. Contributions welcome.
I was primarily thinking of the use for reviewers (and admins, assistant
chairs, etc.), for whom I guess one could show all diffs, at least whenever
a notification mail would have been sent?
For authors, perhaps the right thing would be diffs while reviews are
visible to them, and when they become visible since the last time they were
(e.g. to pick up changes between author response and final reviews)? As
an author, I typically dump as .txt and run diff manually for the final
reviews.
Peter
… —
Reply to this email directly, view it on GitHub
<#320 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABFMZZW6XH436C4K5YAA7ELXZRQXTANCNFSM6AAAAAA4RIZXHM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The API endpoint |
It'd be really useful to be able to see the changes when reviewers update their reviews - perhaps just by appending a diff of the before and after text-rendered review to emails?
The text was updated successfully, but these errors were encountered: