chore: update path glob pattern for e2e test execution triggers

* Added test/** directory to the glob pattern for running e2e tests
* Fixed pattern for Go files from ***/*.go to **/*.go for proper glob matching
* Ensures e2e tests are triggered when relevant test files are modified

Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>

Update docs/content/docs/install/getting-started.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>

Author: chmouel

.tekton/e2e-label.yaml

@@ -8,7 +8,7 @@ metadata:
     pipelinesascode.tekton.dev/cancel-in-progress: "true"
     pipelinesascode.tekton.dev/on-event: "pull_request"
     pipelinesascode.tekton.dev/on-target-branch: "main"
-    pipelinesascode.tekton.dev/on-path-change: "[***/*.go, .github/workflows/*l]"
+    pipelinesascode.tekton.dev/on-path-change: "[**/*.go, .github/workflows/*l, test/**]"
 spec:
   pipelineSpec:
     tasks:

docs/content/docs/guide/cli.md

@@ -128,6 +128,9 @@ internet connection. In this scenario, it will set up a forwarding URL on
 will not prompt you unless you explicitly specify the `--force-gosmee` flag
 (which can be useful if you are running [OpenShift Local](https://developers.redhat.com/products/openshift-local/overview) for instance).
 
+gosmee is by no means to be used in production, but it can be useful for
+testing.
+
 {{< /details >}}
 
 {{< details "tkn pac bootstrap github-app" >}}
@@ -164,7 +167,8 @@ questions if you want to configure a webhook for your provider of choice.
 `tkn pac delete repo` -- will delete a Pipelines-as-Code Repository definition.
 
 You can specify the flag `--cascade` to optionally delete the attached secrets
-(ie: webhook or provider secret) to the Pipelines-as-Code Repository definition.
+(i.e. webhook or provider secret) to the Pipelines-as-Code Repository
+definition.
 
 {{< /details >}}
 

docs/content/docs/install/getting-started.md

@@ -66,7 +66,8 @@ not running on OpenShift.
 
 This is not required, but considering the need to have GitHub reach our
 Pipelines-as-Code controller from the internet, using `gosmee` is the most
-straightforward way to do it.
+straightforward way to do it. Note that while gosmee lets you get started
+quickly, it is not intended for production use.
 
 ```console
 Pipelines-as-Code does not install an Ingress object to allow the controller to be accessed from the internet.

docs/content/docs/install/installation.md

@@ -140,9 +140,16 @@ You can use following command to update the envs on the controller
 
 ## Proxy service for PAC controller
 
-Pipelines-as-Code requires an externally accessible URL to receive events from Git providers.
-If you're developing locally (such as on kind or Minikube) or don't want to set up an ingress on your cluster,
-you can also use a proxy service to expose the `pipelines-as-code-controller` service and allow it to receive events.
+Pipelines-as-Code requires an externally accessible URL to receive events from
+Git providers. If you're developing locally (such as on kind or Minikube) or
+cannot set up an ingress on your cluster, you can also use a proxy service to
+expose the `pipelines-as-code-controller` service and allow it to receive
+events.
+
+This is useful for testing and development purposes, but not recommended for
+production, since gosmee and the platform running
+<https://hook.pipelinesascode.com>
+have no support or security guarantees.
 
 ### Proxying with hook.pipelinesascode.com