Repository navigation
Conversation
|
tested in #14 with hide-after-days 0
|
ccd0b99 to
ca81308
Compare
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
ca81308 to
dd4d856
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
ACK dd4d856 (automated): reviewed 1 commit |
yuval-block
left a comment
There was a problem hiding this comment.
code ACK but i'm not 100% sure about concept ACK, I opened the issue this closes based on a hunch that this would become annoying so seeking concept ACK from other contributors to the project (@arminsabouri ?). the hide-after-days and its default value in particular makes sense to me.
an alternative approach would be to update the initial comment but i think i prefer this approach even though it's more spammy because it clarifies the chronology.
dd4d856 to
8b0baec
Compare
range-diff for force push dd4d856d15 → 8b0baeca96
|
8b0baec to
51dc3fc
Compare
range-diff for force push 8b0baeca96 → 51dc3fc2a6
|
51dc3fc to
d743ce0
Compare
range-diff for force push 51dc3fc2a6 → d743ce0463
|
Earlier range-diff comments at least hide-after-days old (three by default) are minimized as outdated, so a long pull request stays readable.
d743ce0 to
39bceb1
Compare
range-diff for force push d743ce0463 → 39bceb106f
|
|
ACK 39bceb1
|

closes #3: on a force push, earlier range-diff comments at least hide-after-days old (three by default) are hidden as outdated.