Merge pull request #37508 from openshift-cherrypick-robot/cherry-pick…

…-36558-to-enterprise-4.8

[enterprise-4.8] RHDEVDOCS-3108: Document the integrated import flow

modules/odc-importing-codebase-from-git-to-create-application.adoc

@@ -15,7 +15,14 @@ The following procedure walks you through the *From Git* option in the *Develope
 * *Context Dir* to specify the subdirectory for the application source code you want to use to build the application.
 * *Source Secret* to create a *Secret Name* with credentials for pulling your source code from a private repository.
 
-. In the *Builder* section, after the URL is validated, an appropriate builder image is detected, indicated by a star, and automatically selected. For the `https://github.com/sclorg/nodejs-ex` Git URL, the Node.js builder image is selected by default. If a builder image is not auto-detected, select a builder image. If required, you can change the version using the *Builder Image Version* drop-down list.
+. Optional: You can import a devfile, a Dockerfile, or a builder image through your Git repository to further customize your deployment.
+* If your Git repository contains a devfile, a Dockerfile, or a builder image, it is automatically detected and populated on the respective path fields. If a devfile, a Dockerfile, and a builder image are detected in the same repository, the devfile is selected by default.
+* To edit the file import type and select a different strategy, click *Edit import strategy* option.
+* If multiple devfiles, Dockerfiles, or builder images are detected, to import a specific devfile, Dockerfile, or a builder image, specify the respective paths relative to the context directory.
+
+. After the Git URL is validated, the recommended builder image is selected and marked with a star. If the builder image is not auto-detected, select a builder image. For the `https://github.com/sclorg/nodejs-ex` Git URL, by default the Node.js builder image is selected.
+.. Optional: Use the *Builder Image Version* drop-down to specify a version.
+.. Optional: Use the *Edit import strategy* to select a different strategy.
 
 . In the *General* section:
 .. In the *Application* field, enter a unique name for the application grouping, for example, `myapp`. Ensure that the application name is unique in a namespace.