Skip to content

Commit

Permalink
Point at images hosted on the demo site instead of shipping images in…
Browse files Browse the repository at this point in the history
… the gem
  • Loading branch information
jagthedrummer committed Nov 22, 2024
1 parent c8fd337 commit 05c1c55
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions bullet_train/docs/upgrades.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down

0 comments on commit 05c1c55

Please sign in to comment.