-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Group Label Changed Comments in timeline #13304
Conversation
Codecov Report
@@ Coverage Diff @@
## master #13304 +/- ##
=======================================
Coverage 42.13% 42.14%
=======================================
Files 689 689
Lines 75764 75810 +46
=======================================
+ Hits 31926 31948 +22
- Misses 38611 38629 +18
- Partials 5227 5233 +6
Continue to review full report at Codecov.
|
Co-authored-by: zeripath <art27@cantab.net>
@pta2002 please update your branch. (In general it is a better and easier if you allow maintainers to update the branch.) |
Done, how'd I allow maintainers to update the branch in the future? |
Unfortunately it needs another update |
🚀 |
…s-stored-in-email-address-table * origin/master: [UI] Hide consecutive additions and removals of the same label (go-gitea#13315) [skip ci] Updated translations via Crowdin Fix send mail (go-gitea#13312) [skip ci] Updated translations via Crowdin Deny wrong pull (go-gitea#13308) Group Label Changed Comments in timeline (go-gitea#13304) [skip ci] Updated translations via Crowdin Attempt to handle unready PR in tests (go-gitea#13305) go-gitea#12897 - add mastodon provider (go-gitea#13293) [skip ci] Updated translations via Crowdin Fix Storage mapping (go-gitea#13297) Update Mirror IsEmpty status on synchronize (go-gitea#13185) Fix bug isEnd detection on getIssues/getPullRequests (go-gitea#13299) systemd service: Add commented PATH environment option for Git prefix (go-gitea#13170) Sendmail command (go-gitea#13079) Various UI and arc-green fixes (go-gitea#13291)
This targets issue #13268, by grouping label changed comments in an issue's timeline, similar to how GitHub does it. Here's an example: