If the intention of a RotationAction is primarily to move/rename a file, then I am not really sure that having multiple of them makes a lot of since.  I can see having other actions, like sending an event that rotation has finished, but I personally would rather represent it as a RotationAction that wraps another one.  Just so it can have more control over the order in which operations, like a move, happen.

This is not critical, just curious for your thoughts on this.