Skip to content
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

notifications from a bot caused by a bot making a comment are not shown in search bot:true #1971

phil-davis opened this issue Aug 7, 2019 · 1 comment


Copy link

commented Aug 7, 2019

Are you experiencing this issue in or your own instance?

  • My instance

If your issue is related to an subscription purchase please ensure you have installed the Octobox GitHub App for the repositories concerned.

🐞 Problem
I have a repo that I am following where the "lock" bot has been enabled. It is currently gradually (~100 per hour) locking about 30,000 old issues and pull requests. It puts a comment as it locks each thread. That generates a notification. Those notifications are very annoying and will come for the next few weeks!

When I click on "Bots" I was expecting to see "Search notifications generated by GitHub apps or bot users (name ends in '-bot')" as described in the help. e.g. the lock bot is the one that makes the new comment in the thread, and thus the lock bot is the "cause of the notification".

But actually I only see notifications for issues/PRs that were created (are owned by?) by a bot - e.g. dependabot.

🎯 Goal
Be able to search for and see all notifications that are "caused" ("generated"? is that the same thing) by a bot. Then be able to mark them all as read, or otherwise archive or dispose of them quickly. Then I can get on with reading "real" notifications of interest.

💡 Possible solutions

I have not looked at the API data available, but hopefully for comment notifications the name of the user/bot that made the comment is accessible somewhere. Then that can be used in the code that selects "notifications by a bot".

📋 Steps to solve the problem

  • Comment below about what you've started working on.
  • Add, commit, push your changes
  • Submit a pull request and add this in comments - Addresses #<put issue number here>
  • Ask for a review in comments section of pull request
  • Celebrate your contribution to this project 🎉

This comment has been minimized.

Copy link

commented Aug 7, 2019

@phil-davis this would be great to have, but also very tricky because that information isn't easily available via the GitHub API, so we'd have to try and reconstruct a full timeline of events for each notification and look at what possibly could have caused that notification to be sent.

In the short term, you can filter notifications by locked which might help:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.