Changes for RHDEVDOCS-4827 with SME QE and peer review

Author: shreyasiddhartha

cicd/pipelines/using-pipelines-as-code.adoc

@@ -48,4 +48,6 @@ include::modules/op-customizing-pipelines-as-code-configuration.adoc[leveloffset
 
 * xref:../../cli_reference/tkn_cli/installing-tkn.adoc#installing-tkn[Installing tkn]
 
-* xref:../../cicd/pipelines/op-release-notes.adoc#op-release-notes[{pipelines-title} release notes]
+* xref:../../cicd/pipelines/op-release-notes.adoc#op-release-notes[{pipelines-title} release notes]
+
+* xref:../../applications/creating_applications/odc-creating-applications-using-developer-perspective.adoc#odc-creating-applications-using-the-developer-perspective[Creating applications using the Developer perspective]

modules/odc-adding-a-GitHub-repository-containing-pipelines.adoc

@@ -3,7 +3,7 @@
 
 = Adding a GitHub repository containing pipelines
 
-In the developer perspective, you can add your GitHub repository containing pipelines to the {product-title} cluster. This allows you to run pipelines and tasks from your GitHub repository on the cluster when relevant Git events, such as push or pull requests are triggered.
+In the *Developer* perspective, you can add your GitHub repository containing pipelines to the {product-title} cluster. This allows you to run pipelines and tasks from your GitHub repository on the cluster when relevant Git events, such as push or pull requests, are triggered.
 
 [NOTE]
 ====
@@ -14,7 +14,7 @@ You can add both public and private GitHub repositories.
 * Ensure that your cluster administrator has configured the required GitHub applications in the administrator perspective.
 
 .Procedure
-. In the developer perspective, choose the namespace or project in which you want to add your GitHub repository.
+. In the *Developer* perspective, choose the namespace or project in which you want to add your GitHub repository.
 . Navigate to *Pipelines* using the left navigation pane.
 . Click *Create* -> *Repository* on the right side of the Pipelines page.
 . Enter your *Git Repo URL* and the console automatically fetches the repository name.
@@ -51,3 +51,8 @@ image::Git-access-token-secret.png[]
 . Navigate back to the developer console and click *Add*.
 . Read the details of the steps that you have to perform and click *Close*.
 . View the details of the repository you just created.
+
+[NOTE]
+====
+When importing an application using *Import from Git* and the Git repository has a `.tekton` directory, you can configure `pipelines-as-code` for your application.
+====

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

@@ -21,10 +21,11 @@ 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.
 
-. 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.
+. 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`, or 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.
+* If multiple `Devfiles`, a `Dockerfiles`, or a `Builder Images` are detected, to import a specific instance, 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.
@@ -51,7 +52,17 @@ The resource name must be unique in a namespace. Modify the resource name if you
 You can set the default resource preference for Import by browsing the User Preferences page and clicking *Applications* -> *Resource type* field. The *Serverless Deployment* option is displayed in the *Import from Git* form only if the {ServerlessOperatorName} is installed in your cluster. For further details, refer to the {ServerlessProductName} documentation.
 ====
 
-. In the *Pipelines* section, select *Add Pipeline*, and then click *Show Pipeline Visualization* to see the pipeline for the application. A default pipeline is selected, but you can choose the pipeline you want from the list of available pipelines for the application.
+. In the *Pipelines* section, select *Add Pipeline*, and then click *Show Pipeline Visualization* to see the pipeline for the application. A default pipeline is selected, but you can choose the pipeline you want from the list of available pipelines for the application. If *Configure PAC* is checked and the GitHub App is set up, you can see *Use GitHub App* and *Setup a webhook* options. If GitHub App is not set up, you can see *Setup a webhook* option.
++
+[NOTE]
+====
+The *Add pipeline* checkbox is checked and *Configure PAC* is selected by default if the following criterias are fulfilled:
+
+* Pipeline operator is installed
+* `pipelines-as-code` is enabled
+* `.tekton` directory is detected in the Git repository
+
+====
 
 . Optional: In the *Advanced Options* section, the *Target port* and the *Create a route to the application* is selected by default so that you can access your application using a publicly available URL.
 +

modules/op-configuring-pipelines-as-code-for-a-github-app.adoc

@@ -9,6 +9,12 @@
 [role="_abstract"]
 GitHub Apps act as a point of integration with {pipelines-title} and bring the advantage of Git-based workflows to OpenShift Pipelines. Cluster administrators can configure a single GitHub App for all cluster users. For GitHub Apps to work with Pipelines as Code, ensure that the webhook of the GitHub App points to the Pipelines as Code event listener route (or ingress endpoint) that listens for GitHub events.
 
+[NOTE]
+====
+When importing an application using *Import from Git* and the Git repository has a `.tekton` directory, you can configure `pipelines-as-code` for your application.
+====
+
+
 [id="configuring-github-app-for-pac"]
 == Configuring a GitHub App