Status: Closed (View Workflow)
Affects Version/s: None
Fix Version/s: None
In Git version control system it is possible to change history (e.g. to remove accidentally added files which are big/confidential/infringing), or completely delete a branch without a trace (e.g. remove already merged or abandoned feature branches) . This can be useful, but may be dangerous.
What if someone does that by accident or with malicious intent? In corporate settings, surprises are usually not a good thing, especially when it comes to data loss/corruption.
Within our corporate environment we have to rely on unmodified history within our PUSHED repositories to be able to repoduce historical situations exactly.
Wouldn't it be possible for STASH to reject history changes?