Because we're not organizationally at a place where we are ready to auto-deploy without any checks, we need to make sure that there is clear communication about the "next steps" after a release is created. In addition, we want to add clear communication about successes and points of failure.
This PR overhauls the reporting system, bringing it more out of github actions and into a report that shows up on the PR after it is complete.
Any PRs that failed to create (and what repo they were in)
A copyable command line command to approve all the PRs created (this is a great way to track who triggered the update so that they can be a point of contact if further action needs to happen).
Clear instructions on how to revert the changes if something goes wrong.
Because we're not organizationally at a place where we are ready to auto-deploy without any checks, we need to make sure that there is clear communication about the "next steps" after a release is created. In addition, we want to add clear communication about successes and points of failure.
This PR overhauls the reporting system, bringing it more out of github actions and into a report that shows up on the PR after it is complete.
Here is an example from one of my tests: https://github.com/planningcenter/test-js-auto-deploy-pkg/pull/5
It shows: