[not_your_vase]

As one example, if your work on something that's audited, this can be useful, for the papertrail: you document (in an enforced way) when and who worked on the different stages of a piece code, which also gives you some extra info when doing failure root cause analysis (where did it go wrong by whom).

On projects which are done in the style of code-quick-test-in-prod I think it is usually less useful.

[harshithmul]

Ahh, yeah paper trail makes sense. But the ownership aspect of where it went wrong can we understand without the workflow restrictions also right?