-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[impovement] don't reverence same issue multible times next to itself #8722
Comments
@guillep2k didn't you write code in this area, so do you have any idears where to look at? |
Every time you edit the comment it will invalidate previous references and create them anew. The reasons are because previous ones could or could not be the same as the new ones, and because I thought a trail would be good for consistency. The algorithm could be more sophisticated and detect "exact same list", of course. At the time it didn't seem too important. In this case, only a few minutes passed between one edition and the next, but what if days have passed? Mails will have been sent, people will have read that, etc. It made sense to me to leave a trail of changes, but I guess it can be confusing. I don't know: it's a feature? a bug? 😁 |
to have a trail is nice ... but add one check if it is next to itself and update instead? is this hard to do? |
@6543 on it. |
just look at: https://gitea.com/gitea/tea/pulls/45
Gitea Version: 1.11.0+dev-56-g28f60bb5c
The text was updated successfully, but these errors were encountered: