RFR: 2312: Do not require re-review for a simple merge [v3]
Erik Joelsson
erikj at openjdk.org
Tue Jul 9 10:24:04 UTC 2024
On Tue, 9 Jul 2024 10:20:21 GMT, Pavel Rappo <prappo at openjdk.org> wrote:
>> If a repository is configured to ignore stale reviews, every commit to a PR made against that repo means that the PR needs to be re-reviewed. Re-reviewing is costly, and not all commits are worth that cost.
>>
>> One example of such a commit is a simple merge. During a PR's lifetime, the PR's target branch (typically, repo's `master`) might be merged into the PR multiple times. Usually, such merges are trivial and would effectively be performed by Skara automatically if the PR didn't have them in the first place [^*]. For such commits, it makes sense to not require review.
>>
>> This is my first contribution to Skara domain logic, which I've just started learning about. Also, while I tried to code this change according to Skara customs and idioms, I might have missed something. I guess what I'm saying is **take extra care** reviewing this PR. Thanks.
>>
>>
>> [^*]: This is the main assumption of this PR. Any simple merges present in a PR change the end result of that PR insignificantly, if at all.
>
> Pavel Rappo has updated the pull request incrementally with one additional commit since the last revision:
>
> Respond to feedback
>
> Pulls up new methods from GitRepository.
I like that you are abstracting out the logic for review coverage into a separate class. See inline for comments and thoughts.
-------------
PR Review: https://git.openjdk.org/skara/pull/1672#pullrequestreview-2165659932
More information about the skara-dev
mailing list