Update docs to point to ui.digger.dev (#2024)

* Update docs to point to ui.digger.dev

* Update docs/ce/getting-started/github-actions-+-aws.mdx

* Update docs/ce/getting-started/github-actions-+-aws.mdx

* Update docs/ce/getting-started/github-actions-and-gcp.mdx

* Update docs/ce/getting-started/github-actions-and-gcp.mdx

* Update docs/ce/getting-started/github-actions-and-gcp.mdx

Co-authored-by: bismuthdev[bot] <177057995+bismuthdev[bot]@users.noreply.github.com>

* Update docs/ce/getting-started/github-actions-and-gcp.mdx

Co-authored-by: bismuthdev[bot] <177057995+bismuthdev[bot]@users.noreply.github.com>

* Update github-actions-+-aws.mdx

---------

Co-authored-by: Mohamed Habib <[email protected]>
Co-authored-by: bismuthdev[bot] <177057995+bismuthdev[bot]@users.noreply.github.com>

Author: 3 people

docs/ce/getting-started/github-actions-+-aws.mdx

@@ -8,7 +8,16 @@ In this tutorial, you will set up Digger to automate terraform pull requests usi
 
 - A GitHub repository with valid terraform code. Here's a [demo repo](https://github.com/diggerhq/quickstart-actions-aws)
 - Your AWS credentials. See [Hashicorp's AWS tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/aws-build)
-- Digger [GitHub App](https://github.com/apps/digger-cloud/installations/select_target) installed
+
+# Step 1: create your Digger account
+
+Head to [ui.digger.dev](https://ui.digger.dev) and sign up using your preferred method.
+
+You should see onboarding screen after you sign up, which guides you to install the github app and perform the next steps
+
+# Step 2: install the Digger GitHub App
+
+Install the Digger [GitHub App](https://github.com/apps/digger-pro) into your repository.
 
 <Note>
 Digger GitHub App does not need access to your cloud account, it just starts jobs in your CI. All sensitive data stays in your CI job.
@@ -17,14 +26,14 @@ You can also [self-host Digger orchestrator](/ce/self-host/deploy-docker) with a
 
 </Note>
 
-# Create Action Secrets with AWS credentials (you can also [use OIDC](/ce/cloud-providers/authenticating-with-oidc-on-aws))
+# Step 3: Create Action Secrets with AWS credentials (you can also [use OIDC](/ce/cloud-providers/authenticating-with-oidc-on-aws)
 
 In GitHub repository settings, go to Secrets and Variables - Actions. Create the following secrets:
 
 - `AWS_ACCESS_KEY_ID`
 - `AWS_SECRET_ACCESS_KEY`
 
-# Create digger.yml
+# Step 4: Create digger.yml
 
 This file contains Digger configuration and needs to be placed at the root level of your repository. Assuming your terraform code is in the `prod` directory:
 
@@ -34,7 +43,7 @@ projects:
   dir: prod
 ```
 
-# Create Github Actions workflow file
+# Step 5: Create Github Actions workflow file
 
 Place it at `.github/workflows/digger_workflow.yml` (name is important!)
 
@@ -78,7 +87,7 @@ jobs:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 ```
 
-# Create a PR to verify that it works
+# Step 6: Create a PR to verify that it works
 
 Terraform will run an existing plan against your code.
 

docs/ce/getting-started/github-actions-and-gcp.mdx

@@ -8,7 +8,16 @@ In this tutorial, you will set up Digger to automate terraform pull requests usi
 
 - A GitHub repository with valid terraform code. Here's a [demo repo](https://github.com/diggerhq/demo-conftest-gcp/) for inspiration.
 - A GCP Service Account Key json file. See [Hashicorp's GCP tutorial](https://developer.hashicorp.com/terraform/tutorials/gcp-get-started/google-cloud-platform-build)
-- Digger [GitHub App](https://github.com/apps/digger-cloud/installations/select_target) installed
+
+# Step 1: create your Digger account
+
+Head to [ui.digger.dev](https://ui.digger.dev) and sign up using your preferred method.
+
+You should see onboarding screen after you sign up, which guides you to install the github app and perform the next steps
+
+# Step 2: install the Digger GitHub App
+
+Install the Digger [GitHub App](https://github.com/apps/digger-pro) into your repository.
 
 <Note>
 Digger GitHub App does not need access to your cloud account, it just starts jobs in your CI. All sensitive data stays in your CI job.
@@ -17,13 +26,13 @@ You can also [self-host Digger orchestrator](/self-host/deploy-docker) with a pr
 
 </Note>
 
-# Create Action Secrets
+# Step 3: Create Action Secrets
 
 In GitHub repository settings, go to Secrets and Variables - Actions. Create the following secrets:
 
-- `GCP_CREDENTIALS` - contents of your GCP Service Account Key json file. You can also [use OIDC](/gcp/federated-oidc-access/))
+- `GCP_CREDENTIALS` - contents of your GCP Service Account Key json file. You can also [use OIDC](/ce/gcp/federated-oidc-access/)
 
-# Create digger.yml
+# Step 4: Create digger.yml
 
 This file contains Digger configuration and needs to be placed at the root level of your repository. Assuming your terraform code is in the `prod` directory:
 
@@ -33,7 +42,7 @@ projects:
   dir: prod
 ```
 
-# Create Github Actions workflow file
+# Step 5: Create Github Actions workflow file
 
 Place it at `.github/workflows/digger_workflow.yml` (name is important!)
 
@@ -93,7 +102,7 @@ This file defines a workflow with 5 steps:
 - Verify that GCP is configured correctly by running `gcloud info`
 - Run Digger.
 
-# Create a PR to verify that it works
+# Step 6: Create a PR to verify that it works
 
 Make any change to your terraform code e.g. add a blank line. An action run should start (you can see log output in Actions). After some time you should see output of Terraform Plan added as a comment to your PR: