change / to /login/

code-quality/ci-setup/general.md

@@ -91,7 +91,7 @@ You can also explicitly set the upstream branch if needed via `--upstream`, but
 
 ### Uploading Results From Hourly/Nightly Builds
 
-Trunk Code Quality has the ability to post its results to [app.trunk.io](https://app.trunk.io/?intent=code+quality). This will enable you to view your repository's Code Quality history over time so you can track the trend of issues in your code, as well as browse the issues in your repository to help you understand which issues should be prioritized to fix.
+Trunk Code Quality has the ability to post its results to [app.trunk.io](https://app.trunk.io/login/?intent=code+quality). This will enable you to view your repository's Code Quality history over time so you can track the trend of issues in your code, as well as browse the issues in your repository to help you understand which issues should be prioritized to fix.
 
 In order to keep the data up-to-date, you should upload Trunk Code Quality results regularly in an automated fashion. Depending on the size of your repository and the linters you have configured to run, running Trunk Code Quality on your whole repository may take a while. Because this run may take a while, we recommend uploading Trunk Code Quality results once daily. However, the system supports uploading results for every commit, so the granularity of upload is up to you.
 

code-quality/overview/how-does-it-work.md

@@ -58,6 +58,6 @@ Trunk works in CI. Trunk Code Quality provides [GitHub integration](../ci-setup/
 
 ### Nightly reports
 
-Trunk Code Quality allows you to [upload results](../ci-setup/manual-setup.md#other-providers) to the [Trunk Web App](https://app.trunk.io/?intent=code+quality), which provides a dashboard for you to view your current code base issues and track code base health over time.
+Trunk Code Quality allows you to [upload results](../ci-setup/manual-setup.md#other-providers) to the [Trunk Web App](https://app.trunk.io/login/?intent=code+quality), which provides a dashboard for you to view your current code base issues and track code base health over time.
 
 [Learn more about nightly reporting.](how-does-it-work.md#nightly-reports)

code-quality/security.md

@@ -19,7 +19,7 @@ Whether invoked directly by developers on their local machines, triggered automa
 
 The Trunk VS Code extension has the same privacy properties as the Trunk CLI. Under the hood, all code-checking by the VS Code extension is completed via the Trunk CLI, which drives the VS Code extension.
 
-### Web App ([app.trunk.io](https://app.trunk.io/?intent=code+quality))
+### Web App ([app.trunk.io](https://app.trunk.io/login/?intent=code+quality))
 
 The Trunk Code Quality web app is powered via running nightly scans in your repo’s own CI system which uploads results to the Trunk backend. This feature is optional, but it enables you to audit the issues in your repo and prioritize fixes. Here's how it works:
 

flaky-tests/get-started/README.md

@@ -4,7 +4,7 @@
 
 Trunk Flaky Tests works by changing all of your CI jobs that run tests to upload their test results to Trunk. This setup looks slightly different depending on which CI system and test framework(s) you use, but we have guides for all the popular systems.
 
-### 1. Sign up for [app.trunk.io](https://app.trunk.io/?intent=flaky+tests)
+### 1. Sign up for [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests)
 
 You must create an account and Trunk organization to complete the steps below. 
 
@@ -24,7 +24,7 @@ Once you've merged changes to your CI test jobs, make sure you've run at least 1
 
 ### 4. Confirm your configuration, analyze your dashboard
 
-In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), select the repo you're working in, and navigate to `Flaky Tests` -> `Uploads`. Confirm that you see the upload(s) from the previous step.
+In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), select the repo you're working in, and navigate to `Flaky Tests` -> `Uploads`. Confirm that you see the upload(s) from the previous step.
 
 Trunk needs to ingest a large amount of test data from a variety of pull request branches and protected branches (like `main` or `master`) before it can start accurately detecting flaky tests. This may happen quickly if you have a very high-velocity repo and run test jobs hundreds of times a day.
 

flaky-tests/get-started/ci-providers/buildkite.md

@@ -12,7 +12,7 @@ Before you start on these steps, see the [Test Frameworks](../frameworks/) docs
 
 ### 1. Store a TRUNK\_TOKEN secret in your CI system
 
-In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
 
 **`Settings` -> `Manage Organization` -> `Organization API Token`**
@@ -21,7 +21,7 @@ Store your API Token in a [Buildkite CI secret](https://buildkite.com/docs/pipel
 
 ### 2. Grab your Organization Slug
 
-To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
  **`Settings` -> `Manage` -> `Organization` -> `Organization Slug`**
 

flaky-tests/get-started/ci-providers/circleci.md

@@ -12,15 +12,15 @@ Before you start on these steps, see the [Test Frameworks](../frameworks/) docs
 
 ### 1. Store a TRUNK\_TOKEN secret in your CI system
 
-In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
 **`Settings` -> `Manage Organization` -> `Organization API Token`**
 
 Store your API Token in your CircleCI project settings under  **Environment Variables** as a new variable  named `TRUNK_TOKEN`. Make sure you are getting your _organization token_, not your project/repo token.
 
 ### 2. Grab your Organization Slug
 
-To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
  **`Settings` -> `Manage` -> `Organization` -> `Organization Slug`**
 

flaky-tests/get-started/ci-providers/droneci.md

@@ -12,15 +12,15 @@ Before you start on these steps, see the [Test Frameworks](../frameworks/) docs
 
 ### 1. Store a TRUNK\_TOKEN secret in your CI system
 
-In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
 **`Settings` -> `Manage Organization` -> `Organization API Token`**
 
 Store your API Token in your Drone CI project settings as a new variable named `TRUNK_TOKEN`. Make sure you are getting your _organization token_, not your project/repo token.
 
 ### 2. Grab your Organization Slug
 
-To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
  **`Settings` -> `Manage` -> `Organization` -> `Organization Slug`**
 

flaky-tests/get-started/ci-providers/github-actions.md

@@ -12,15 +12,15 @@ Before you start on these steps, see the [Test Frameworks](../frameworks/) docs
 
 ### 1. Store a TRUNK\_TOKEN secret in your CI system
 
-In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
 **`Settings` -> `Manage Organization` -> `Organization API Token`**
 
 Store your API Token in a [GitHub secret](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) named `TRUNK_TOKEN`.
 
 ### 2. Grab your Organization Slug
 
-To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
  **`Settings` -> `Manage` -> `Organization` -> `Organization Slug`**
 

flaky-tests/get-started/ci-providers/gitlab.md

@@ -12,15 +12,15 @@ Before you start on these steps, see the [Test Frameworks](../frameworks/) docs
 
 ### 1. Store a TRUNK\_TOKEN secret in your CI system
 
-In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
 **`Settings` -> `Manage Organization` -> `Organization API Token`**
 
 Store your API Token in a [GitLab Variable](https://docs.gitlab.com/ee/ci/variables/index.html#for-a-project) for your `TRUNK_TOKEN` by navigating to your GitLab project's **Settings** > **CI/CD** > **Variables**. 
 
 ### 2. Grab your Organization Slug
 
-To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
  **`Settings` -> `Manage` -> `Organization` -> `Organization Slug`**
 

flaky-tests/get-started/ci-providers/jenkins.md

@@ -12,15 +12,15 @@ Before you start on these steps, see the [Test Frameworks](../frameworks/) docs
 
 ### 1. Store a TRUNK\_TOKEN credential in your CI system
 
-In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
 **`Settings` -> `Manage Organization` -> `Organization API Token`**
 
 From your Jenkins dashboard, store your API Token in a credential named `TRUNK_TOKEN`. 
 
 ### 2. Grab your Organization Slug
 
-To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
  **`Settings` -> `Manage` -> `Organization` -> `Organization Slug`**
 

flaky-tests/get-started/ci-providers/otherci.md

@@ -12,15 +12,15 @@ Before you start on these steps, see the [Test Frameworks](../frameworks/) docs
 
 ### 1. Store a TRUNK\_TOKEN secret in your CI system
 
-In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
 **`Settings` -> `Manage Organization` -> `Organization API Token`**
 
 Store your API Token as a secret named `TRUNK_TOKEN` in your CI system's secrets or variables manager.
 
 ### 2. Grab your Organization Slug
 
-To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
  **`Settings` -> `Manage` -> `Organization` -> `Organization Slug`**
 

flaky-tests/get-started/ci-providers/semaphoreci.md

@@ -12,15 +12,15 @@ Before you start on these steps, see the [Test Frameworks](../frameworks/) docs
 
 ### 1. Store a TRUNK\_TOKEN secret in your CI system
 
-In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
 **`Settings` -> `Manage Organization` -> `Organization API Token`**
 
 From your Semaphore dashboard, store your API Token in a secret named `TRUNK_TOKEN`. 
 
 ### 2. Grab your Organization Slug
 
-To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
  **`Settings` -> `Manage` -> `Organization` -> `Organization Slug`**
 

flaky-tests/get-started/ci-providers/travisci.md

@@ -12,15 +12,15 @@ Before you start on these steps, see the [Test Frameworks](../frameworks/) docs
 
 ### 1. Store a TRUNK\_TOKEN secret in your CI system
 
-In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
 **`Settings` -> `Manage Organization` -> `Organization API Token`**
 
 Store your API Token a secret named `TRUNK_TOKEN` in your Travis CI project settings.
 
 ### 2. Grab your Organization Slug
 
-To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/?intent=flaky+tests), navigate to:
+To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. To get your organization slug, In [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests), navigate to:
 
  **`Settings` -> `Manage` -> `Organization` -> `Organization Slug`**
 

flaky-tests/github-pull-request-comments.md

@@ -38,7 +38,7 @@ It's recommended that the Trunk GitHub App be used to manage GitHub comments. If
 8.  If everything looks good, scroll down to double check that your Overview for permissions looks something like the image below. If so, create the token.
 
     <figure><img src="../.gitbook/assets/Screenshot 2024-06-12 at 9.52.28 AM.png" alt=""><figcaption></figcaption></figure>
-9. Once the token is generated, go back to the Trunk App ([app.trunk.io](https://app.trunk.io/?intent=flaky+tests) ) > click on your profile > **Settings** > **Manage** (under _Organization_) > **Organization GitHub Token** and enter the copied token into the text field, then finally press **Submit**.
+9. Once the token is generated, go back to the Trunk App ([app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests) ) > click on your profile > **Settings** > **Manage** (under _Organization_) > **Organization GitHub Token** and enter the copied token into the text field, then finally press **Submit**.
 
 You should see comments posted by your service account on your next PR.
 

flaky-tests/readme.md

@@ -68,4 +68,4 @@ To learn more, [learn about our ticketing integrations](jira-integration.md).
 
 ### **Join Trunk Flaky Tests**
 
-Start finding flaky tests today by [signing up for Trunk](https://app.trunk.io/?intent=flaky+tests) or reading our [Getting Started guides](get-started/).
+Start finding flaky tests today by [signing up for Trunk](https://app.trunk.io/login/?intent=flaky+tests) or reading our [Getting Started guides](get-started/).

flaky-tests/uploader.md

@@ -66,7 +66,7 @@ The `trunk` binary should be run from the repository root. If you need to run th
 
 ### Organization not found
 
-If you receive an error that the org slug or API token is not found, double check that the secrets stored in your CI provider are the same as the Organization settings by navigating to **Settings** -> **Manage** -> **Organization** on [app.trunk.io](https://app.trunk.io/?intent=flaky+tests).
+If you receive an error that the org slug or API token is not found, double check that the secrets stored in your CI provider are the same as the Organization settings by navigating to **Settings** -> **Manage** -> **Organization** on [app.trunk.io](https://app.trunk.io/login/?intent=flaky+tests).
 
 Make sure you are getting your _Organization Slug_, not the Organization Name.