Issues, Pull Request: Filter unread

[muescha]

where:

• in issue list
• in pull request list

what i see:

• i can see rows marked as:
  • unread with a blue line and (css class read)
  • read without blue line (css class unread)
    

what i expect:

• an button/setting to hide the read rows to only see the unread

why:

• i like to see all the new comments and new discussions in the repo

known issues:

• i know this can result only in zero/one or some lines per page when too much is hidden. but this ok.

search filter:

• i don't find a search filter how to filter only the unread messages - that would be the best solution ;)

[sindresorhus]

Is there a GitHub search filter for unread status? I couldn't find it: https://help.github.com/en/articles/searching-issues-and-pull-requests

[muescha]

I also can't find it there. I tried brute force for is:read/is:unread And with status:/type:/... But no luck :(

[sindresorhus]

Then you’ll have to send a feature request to GitHub: support@github.com We cannot do this until the search syntax is supported natively.

[muescha]

still requested many times :/

But we can filter the result rows by:

• search result row divs for class: 'read'
• set this divs visibility to hidden

[fregante]

“Unread” threads are just notifications. Open the notifications page, by repo.

[muescha]

i can use it in notifications like: https://github.com/notifications/beta?after=Y3Vyc29yOjUw&query=repo%3Agatsbyjs%2Fgatsby+is%3Aunread+is%3Apr+is%3Aclosed

but there is not the function "open selected"

[muescha]

i can hide the unread rows with calling this line always in console:

document.querySelectorAll(".js-navigation-container:first-child div.Box-row:not(.Box-row--unread)").forEach(el => el.remove());

but this is time consuming, is there any way to add my own scripts into the "Refined Github" ecosystem to have some of the helper functions (api, libs, utils) available?

the idea would be to have my own filter setup in the search box, is:unread -> this filter is also available when i click on the pagination. then read it and apply it if this filter is set. maybe some helper functions from refined github help me with this task, rather then inventing it again

[TheGeniusSavant]

EDITED for clarity.

I, also, would like to see a sort option, something to the effect of...
lastUpdatedBy:USERNAME
...or...
lastCommenter:USERNAME
...that would accept a '!@me' USERNAME, perhaps?