mgibson1121

Hello, The [kpack](https://github.com/pivotal/kpack) team is seeing this problem with our users as well when they try to integrate with Azure DevOps. Just surfacing in case it helps with feature prioritization....

I'm a huge fan of the "Details" panel. @aemengo I may have expressed this point to you when we initially spoke about this RFC. The Details panel is currently organized...

I'd advocate for its inclusion in the `kp` CLI. A common complaint about the developer experience of using kpack is the need to use other tools in conjunction with `kp`....

A bit of additional user validation for this feature. A firmly entrenched CF operations team at McKesson that is playing around with kpack recently enquired about a "hands off" configuration...

From discussion on 6/16. The builder/clusterbuilder may not be the appropriate resources to fix this problem. We are keeping around the issue because there seems to be consensus that setting...

``` Detection Order: ├ Group #1: │ └ paketo-buildpacks/[email protected] │ └ Group #1: │ ├ paketo-buildpacks/[email protected] │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├...

@aemengo The behavior in your bullets is what I would expect. But we can work shop it. I think we achieved incremental value with the first story.