RFR: 2312: Do not require re-review for a simple merge [v6]

duke duke at openjdk.org
Thu Jul 11 16:13:36 UTC 2024


On Wed, 10 Jul 2024 23:08:02 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 four additional commits since the last revision:
> 
>  - Clean up
>  - Cache targetHash as suggested
>  - Cache Review coverage as suggested
>  - Make PullRequest a ctor parameter as suggested

@pavelrappo 
Your change (at version 739c119120aac05ec3c2c0ea0f365988018aa02f) is now ready to be sponsored by a Committer.

-------------

PR Comment: https://git.openjdk.org/skara/pull/1672#issuecomment-2223340275


More information about the skara-dev mailing list