Hi,
After upgrading to Kubeckecks v2.4.2, a change in behavior has led to the tool checking diffs between entire branches rather than the diffs for the code change in the current application. when a source branch is stale, Kubeckecks attempts to display numerous unrelated diffs. this results in increased process time, often leading to out of memory.
This issue does not occur when we roll back to version 2.2.2
This seems like a bug as it clutters our PR reviews with unrelated changes. We're unsure if it's intentional. If so, could you assist us in configuring Kubeckecks to only check diffs for the current code change?
Hi,
After upgrading to Kubeckecks v2.4.2, a change in behavior has led to the tool checking diffs between entire branches rather than the diffs for the code change in the current application. when a source branch is stale, Kubeckecks attempts to display numerous unrelated diffs. this results in increased process time, often leading to out of memory.
This issue does not occur when we roll back to version 2.2.2
This seems like a bug as it clutters our PR reviews with unrelated changes. We're unsure if it's intentional. If so, could you assist us in configuring Kubeckecks to only check diffs for the current code change?