Force pushes can screw up stored reminders

[timbussmann]

As all reminders are stored in the database based on the commit history, if this commit history is changed (via force pushing a different history) this could cause inconsistencies with the reminder database.

e.g.

Original history:

• Create reminder1
• Create reminder2

-> reminder1 and reminder2 are stored in the database

Force pushed history:

• Create reminder1

-> reminder1 will be updated/reapplied while reminder2 remains as originally defined in the database and will be continued to be opened but there is no way to delete the reminder other than recreating it with the same exact id and deleting it afterwards.

Not sure whether there might also be a case where the deletion of a reminder is being removed via a force push and therefore the reminder is again in the repository but not in the database. This depends on what commit information the force push contains as it could also potentially just recreate the reminder if it's listed in the commits.

I haven't encountered or tested such scenarios yet.