You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Collapse large sequences of label, milestone, etc changes #615
I apologize if this has already been mentioned, but I did not see an issue for it.
Sometimes issues get very noisy when labels and milestones are added/removed. They push comments down and make it difficult to see updates to the item that aren't related to the project management side.
It would be nice if these large sequences (excluding comments) could "collapse". Here's an example of what I'm describing.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.
Reacted by Jonas Gierer, Sindre Sorhus, Anthony, Eli Uriegas, Amory Meltzer, Craig Jennings, Niklas Higi, ViRuSTriNiTy, Pierre Ricadat, Glenn 'devalias' Grant and 1 more
I also think references and commits should stay expanded. But hiding title changes, deploys and label changes would be great. Some things like assignments don't occur very often per issue, so I think they should stay expanded too.
Hidden events should be as unobstrusive as possible IMO, perhaps something like this would work:
Clicking the "+" would expand the hidden events
Reacted by fregante, Eli Uriegas and Amory Meltzer
I'd prefer collapsing title changes with title changes, label changes with label changes, milestone changes with milestone changes, project changes with project changes, reviewers changes with reviewers changes and assignees changes with assignees changes.
P.S. The label changes are particularly bad as they're easy to misclick!
Another idea, perhaps we could hide or group events that are reverted in a short period of time, such as closing and re-opening an issue within a few minutes as that's almost always an accident
Another idea, perhaps we could hide or group events that are reverted in a short period of time, such as closing and re-opening an issue within a few minutes as that's almost always an accident
I consider closing/re-opening or restoring and re-deleting a branch to be significant events.
to combined #2384 here, this issue is an exemple of issue noise caused by bots that upgrade dependencies when an issue is mentioned in the release note
stuff like this makes it simply impossible to read anything easily :/
I really like the idea @fregante proposed here, for the projects I would suggest only when they cancel each other out just like most of those (moving a card back and forward between columns)
I'm working on this feature (as per @fregante 's comment), and it's not clear to me what exactly should count as a sequence of actions. So far I have the following ideas:
Don't use sequences at all and handle actions on the whole page
Activity
fregante commentedon Jul 13, 2017
The title changes are definitely annoying so I'd put a vote to hide those, but references from other issues are useful.
jgierer12 commentedon Jul 13, 2017
I also think references and commits should stay expanded. But hiding title changes, deploys and label changes would be great. Some things like assignments don't occur very often per issue, so I think they should stay expanded too.
Hidden events should be as unobstrusive as possible IMO, perhaps something like this would work:

Clicking the "+" would expand the hidden events
hkdobrev commentedon Jul 13, 2017
I'd prefer collapsing title changes with title changes, label changes with label changes, milestone changes with milestone changes, project changes with project changes, reviewers changes with reviewers changes and assignees changes with assignees changes.
P.S. The label changes are particularly bad as they're easy to misclick!
jgierer12 commentedon Jul 13, 2017
Another idea, perhaps we could hide or group events that are reverted in a short period of time, such as closing and re-opening an issue within a few minutes as that's almost always an accident
hkdobrev commentedon Jul 13, 2017
I consider closing/re-opening or restoring and re-deleting a branch to be significant events.
fregante commentedon Jul 14, 2017
Closing/reopening within minutes is probably because of a mistake and IMHO it should be hidden.
Restoring/deleting branches... not sure of when they are ever useful (other than "let's display every event")
sindresorhus commentedon Oct 18, 2017
Pull request welcome if anyone wants to see this feature :)
yakov116 commentedon Feb 7, 2018
Going to give this a bump, could have used this today
Don't hide PR/Issue rename events
fregante commentedon Dec 9, 2018
This could be made part of
hide-useless-commentsand the feature can becomehide-noiseThe logic should already be there. If anyone is interested you probably just need to tweak the selector and update the name/docs.
6 remaining items
fregante commentedon Jul 2, 2019
I made some noise in #2201
Can all those events be hidden? Or just nearby events that cancel each other out?
What do you think about:
And then:
sindresorhus commentedon Jul 25, 2019
What you suggested above sounds good to me.
AnthonyLenglet commentedon Aug 27, 2019
to combined #2384 here, this issue is an exemple of issue noise caused by bots that upgrade dependencies when an issue is mentioned in the release note
FortAwesome/Font-Awesome#15396
stuff like this makes it simply impossible to read anything easily :/
I really like the idea @fregante proposed here, for the projects I would suggest
only when they cancel each other outjust like most of those (moving a card back and forward between columns)fregante commentedon Oct 29, 2019
@AnthonyLenglet Bots may be best handled by #1745
Tiramisu77 commentedon Nov 10, 2019
I'm working on this feature (as per @fregante 's comment), and it's not clear to me what exactly should count as a sequence of actions. So far I have the following ideas:
pradyunsg commentedon May 25, 2020
Flagging that #1745 was closed since straight-up hiding bot comments isn't a good idea (and I agree!).
Coming from pypa/pip#5182 (comment), I think it'd be great to have some way to collapse commit/PR references as well.
issuehunt-oss commentedon Mar 5, 2021
@sindresorhus has rewarded $45.00 to @fregante. See it on IssueHunt