Take care of ISLANDORA-1091 - h/t @dmoses

Preferably not.  Any commits that have hit public should in general be considered untouchable as meddling in the history conflicts downstream repos and any linking as well as destroying sometimes valuable context. There are exceptions of course like when sensitive information is accidentally leaked. Most arguments for constant rebasing is to create a 'nice' history.  This is a secondary concern and for all practical purposes most development commits are easy to use and do not require rebasing for clarity. There is also value in seeing mistakes that have been made in the past so that you don't make them in the future.  That being said I don't see much reason not to rebase if it's code that is solely on one's own fork and has no external references.