From 05c1c551975831107bf82de0f9b96344cceb99c9 Mon Sep 17 00:00:00 2001 From: Jeremy Green Date: Fri, 22 Nov 2024 10:26:59 -0600 Subject: [PATCH] Point at images hosted on the demo site instead of shipping images in the gem --- bullet_train/docs/upgrades.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/bullet_train/docs/upgrades.md b/bullet_train/docs/upgrades.md index 28b5478d0..08905ab72 100644 --- a/bullet_train/docs/upgrades.md +++ b/bullet_train/docs/upgrades.md @@ -35,20 +35,20 @@ For performing the upgrade you have two options: First go to the "Actions" tab on your project and then click on the "↗️ Create Bullet Train Upgrade PR" link on the left. -![Find the GitHub Action](/assets/upgrade-images/1-find-action.png) +![Find the GitHub Action](https://bullettrain.co/assets/upgrade-images/1-find-action.png) Then on the right side of the page click the "Run workflow" button and enter the target version. `1.4.1` for instance. If you don't enter a version number then the action will target the latest version available on GitHub. -![Run the GitHub Action](/assets/upgrade-images/2-run-action.png) +![Run the GitHub Action](https://bullettrain.co/assets/upgrade-images/2-run-action.png) A few seconds after you click the green "Run workflow" button you should see a new action running. -![Running Action](/assets/upgrade-images/3-running-action.png) +![Running Action](https://bullettrain.co/assets/upgrade-images/3-running-action.png) Once the action has completed you should have a new Pull Request that will perform the upgrade. -![Upgrade PR](/assets/upgrade-images/4-upgrade-pr.png) +![Upgrade PR](https://bullettrain.co/assets/upgrade-images/4-upgrade-pr.png) You should review the contents of the pull request, run the tests, and pull down the branch to run it locally.