Issue/comment edit history

[lunny]

[delvh]

I am conflicted about this feature:
I can totally see its value regarding data integrity and traceability.
However, I noticed that I also find it refreshing that Gitea does not track the edit history as small typos can then be deleted without a trace.

[redstonedesigner]

Perhaps as a compromise, there could be a set amount of time where an edit wouldn't be logged (configurable by an administrator) to allow for typographical errors to be caught and corrected.
After that, the edits would be logged as depicted above.

Just my opinion.

[delvh]

That sounds to me like a really good compromise.
I would suggest a timespan of 15-30 minutes as default.
(If you read through the edit history of this message, you can also already see why I think that this is a good compromise 😉 )

[lunny]

That sounds to me like a really good compromise.
I would suggest a timespan of 15-30 minutes as default.
(If you read through the edit history of this message, you can also already see why I think that this is a good compromise 😉 )

Or the time is configuable.

[delvh]

Yes, but I meant as fallback if no time has been specified inside the app.ini.

I would definitely say that this should only be a server-wide setting with no further extensibility because otherwise you can have repositories where you cannot assume the validity of comments which would make this feature in my opinion less useful.

[wxiaoguang]

But do we really need to make it complex? GitHub just saved every change.