Update README.md

README.md

@@ -542,20 +542,7 @@ tomcat
 
 Since renovate does not natively support the ability to extract a sha256 from a file, we need [a custom shell script](./ci/update-sha.sh) in the [postUpgradeTasks](https://docs.renovatebot.com/configuration-options/#postupgradetasks) to calculate the sha256 of our files and update our Dockerfile accordingly.
 
-Post upgrade tasks can only run on self-hosted Renovate instances, so this forces us to run renovate on a properly configured runner (instead of using mend.io's free GitHub app to manage our dependencies). Getting renovate setup locally looks like
-
-```
-npm install -g renovate
-export RENOVATE_REPOSITORIES=islandora-devops/isle-buildkit
-export RENOVATE_TOKEN=your-gh-pat
-export RENOVATE_ALLOWED_POST_UPGRADE_COMMANDS='["bash ci/update-sha.sh \"{{{depName}}}\" \"{{{currentVersion}}}\" \"{{{newVersion}}}\" \"{{{newDigest}}}\""]'
-
-# this will issue a PR with any updates to
-# our docker images that have renovate configured properly
-renovate --platform=github
-```
-
-Versions listed in GitHub tags or releases can use [advanced capture](https://docs.renovatebot.com/modules/manager/regex/#advanced-capture) in the Dockerfile to update the pinned version.
+Post upgrade tasks can only run on self-hosted Renovate instances, so this forces us to run renovate on a properly configured runner (instead of using mend.io's free GitHub app to manage our dependencies). You can trigger renovate by manually running [the GitHub Action defined in the repo]((../.././actions/workflows/renovate.yml).
 
 
 #### Updating Composer