Refined-github: Collapse large sequences of label, milestone, etc changes

[aaronbushnell]

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.

---

IssueHunt Summary

Backers (Total: $50.00)

• issuehunt ($50.00)

Become a backer now!

Or submit a pull request to get the deposits!

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
  

  - Need some help from other developers? Add your repositories on IssueHunt to raise funds.

IssueHunt has been backed by the following sponsors. Become a sponsor

[fregante]

The title changes are definitely annoying so I'd put a vote to hide _those_, but references from other issues are useful.

[jgierer12]

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]

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]

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]

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.

[fregante]

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]

Pull request welcome if anyone wants to see this feature :)

[yakov116]

Going to give this a bump, could have used this today

[fregante]

This could be made part of hide-useless-comments and the feature can become hide-noise

The logic should already be there. If anyone is interested you probably just need to tweak the selector and update the name/docs.

[yakov116]

This could be made part of hide-useless-comments and the feature can become hide-noise

Not sure it should be one. I like the hide-useless-comments however sometimes I need to look at noise.

[fregante]

sometimes I need to look at _noise_.

Hence the _"show 15 useless comments"_ button. Same goes for this issue. It makes sense to have a single button to show all the noise at once, instead of two.

[yakov116]

@bfred-it good point, however I think these are 2 different types of noise.

It makes sense to have a single button to show all the noise at once, instead of two.

Not sure.

Lets hear what others have to say.

[sindresorhus]

I would prefer one button too. Something like "Show 23 useless comments and events".

[issuehunt-app[bot]]

@issuehunt has funded $50.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[fregante]

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:

• Labels: hide all
• Title changes: hide all but the first one (to show its original title)
• Branch deletion: only when they cancel each other out
• Assignments: only when they cancel each other out
• Open/close: only when they cancel each other out
• Milestones: only when they cancel each other out
• Projects: only when they cancel each other out

And then:

• Lock/unlock: leave unchanged
• Project events: 🤷‍♂️ I don't use projects

[sindresorhus]

What you suggested above sounds good to me.

[AnthonyLenglet]

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 out just like most of those (moving a card back and forward between columns)

[fregante]

@AnthonyLenglet Bots may be best handled by https://github.com/sindresorhus/refined-github/issues/1745

[Tiramisu77]

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:

1. Don't use sequences at all and handle actions on the whole page
2. Group actions by date
3. Select all actions between comments

[pradyunsg]

Flagging that #1745 was closed since straight-up hiding bot comments isn't a good idea (and I agree!).

Coming from https://github.com/pypa/pip/issues/5182#issuecomment-603169486, I think it'd be great to have some way to collapse commit/PR references as well.