Issue/comment edit history #6019

Closed
opened 2025-11-02 06:42:56 -06:00 by GiteaMirror · 6 comments
Owner

Originally created by @lunny on GitHub (Sep 18, 2020).

图片
Originally created by @lunny on GitHub (Sep 18, 2020). <img width="306" alt="图片" src="https://user-images.githubusercontent.com/81045/93554816-eaf47c80-f9a6-11ea-8268-db1ba91fee81.png">
GiteaMirror added the type/proposal label 2025-11-02 06:42:56 -06:00
Author
Owner

@delvh commented on GitHub (Aug 31, 2021):

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.

@delvh commented on GitHub (Aug 31, 2021): 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.
Author
Owner

@redstonedesigner commented on GitHub (Aug 31, 2021):

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.

@redstonedesigner commented on GitHub (Aug 31, 2021): 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.
Author
Owner

@delvh commented on GitHub (Sep 1, 2021):

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 😉 )

@delvh commented on GitHub (Sep 1, 2021): 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 :wink: )
Author
Owner

@lunny commented on GitHub (Sep 2, 2021):

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.

@lunny commented on GitHub (Sep 2, 2021): > 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.
Author
Owner

@delvh commented on GitHub (Sep 2, 2021):

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.

@delvh commented on GitHub (Sep 2, 2021): 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.
Author
Owner

@wxiaoguang commented on GitHub (Sep 2, 2021):

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

@wxiaoguang commented on GitHub (Sep 2, 2021): But do we really need to make it complex? GitHub just saved every change.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6019