Morten Torkildsen

I'm hoping that we can define operations on the `package` resource that "papered over" the underlying package revisions. For example: * Creating a new package would mean creating the initial...

The underlying library do allow for "taking over" resources from other resources, but that option is not currently exposed in the kpt cli. We should allow this to happen. As...

We'll hold off a little bit here since it impacts any downstream consumers of kpt.

Updated the PR to switch to 1.18 instead of 1.19. Got feedback that forcing downstream consumers to switch to the absolute latest version could be problematic. As far as I...

@natasha41575 These changes seem fine to me, but I think we want @droot or @mengqiy to verify this.

This is at least partly intended behavior as described in https://github.com/GoogleContainerTools/kpt/pull/3024. But while we don't want to end up creating the first branch through porch (which makes it the default...

This is fixed with https://github.com/GoogleContainerTools/kpt/pull/3472 and https://github.com/GoogleContainerTools/kpt/pull/3473

Comment on this issue copied from different source: > The best way (that I can think of) to solve this would be with the aggregate Package resource. > > When...

Porch currently relies on the clone task for the package to determine the common ancestor for the 3-way merge, so if the package doesn't have a clone task in the...

That task list doesn't look right. I will try to follow the steps and see if I can reproduce it.