-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
None
-
None
-
None
-
uShift Sprint 230
For each rebase, we need to be able to explain what changes are being introduced for release notes, testing, etc. That might be done by showing the log messages for dependencies in the openshift org on GitHub (to verify that a fix in the openshift controller manager is present, for example), using sippy to report the changes in the new container images, etc. It should also be possible to easily re-run the rebase by hand for debugging, so the pull specs should be included somewhere.
- is related to
-
USHIFT-549 Rebase automation - create PR in case of rebase failure
-
- Closed
-
- links to