This change adds a pr_app executable that can be used to run commands
on a review application that is part of the same Heroku Pipeline as the
application on the staging Git remote. If you had a staging application
called my-staging-app, and a review application whose Heroku
application name was my-staging-app-pr-1234, you would tail the logs
with:
pr_app 1234 tail
Review applications don't get an automatic local Git remote, but because
they share a name with the staging application, we can leverage the
naming scheme to build up an app name.
This change adds a
pr_appexecutable that can be used to run commands on a review application that is part of the same Heroku Pipeline as the application on thestagingGit remote. If you had a staging application calledmy-staging-app, and a review application whose Heroku application name wasmy-staging-app-pr-1234, you would tail the logs with:Review applications don't get an automatic local Git remote, but because they share a name with the staging application, we can leverage the naming scheme to build up an app name.