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
Are you experiencing this issue in octobox.io or your own instance?
octobox.io
My instance
馃悶 Problem
Not sure if this is a general issue, but I have historically thought this was happening but never bothered to definitively check. But today, sure enough I was looking for this PR, and confirmed that it does not exist anywhere in the list of Octobox PRs (neither under "My PRs" nor under "Pull Requests" at all (which took quite some scrolling to verify)).
Happy to help debug this in any way I can...also happy to be told that I'm doing something fundamentally silly 馃憤
馃幆 Goal
Ideally Octobox would list every PR in the repo's I'm subscribed to.
Unfortunately your own issues/prs don't generate notifications in the GitHub API unless someone else comments on them, which is why they don't show up.
Ahhhh, okay good to know, and I assume you guys hear complaints related to that API quirk on a regular basis....is there an issue where I can complain about this upstream to Github?
Alternatively, if you think there's a way (I'm completely unfamiliar with the Github API) to just do the equivalent of actually visiting each subscribed repo's PR's page, asking for author:@me, and checking if any are missing from the notifications list..even if it's so expensive to do that we end up having to hide the feature under a special "super refresh" button?
I could be convinced to dump some time into this, but obviously only if you guys think this is even a viable route or worth pursuing at all.
@brunobeltran lots of people have asked for that feature before, so it would be well received.
It shouldn't be to hard to hook up, the main thing you'd need to do is make fake notifications (because they don't exist on GitHub but we want them to show up in the API) for each of your own PRs, which then may get merged with a real notification if someone else comments on your PRs so you don't have duplicates.
Update: advisor suddenly wants me to graduate this quarter, so I won't be able to deal with this one myself. But if it's still around after Christmas, I'll definitely get this working, as it's basically preventing me from using octobox as my one-stop-shop and I love this tool.
Activity
andrew commentedon Oct 1, 2020
Unfortunately your own issues/prs don't generate notifications in the GitHub API unless someone else comments on them, which is why they don't show up.
brunobeltran commentedon Oct 1, 2020
Ahhhh, okay good to know, and I assume you guys hear complaints related to that API quirk on a regular basis....is there an issue where I can complain about this upstream to Github?
Alternatively, if you think there's a way (I'm completely unfamiliar with the Github API) to just do the equivalent of actually visiting each subscribed repo's PR's page, asking for author:@me, and checking if any are missing from the notifications list..even if it's so expensive to do that we end up having to hide the feature under a special "super refresh" button?
I could be convinced to dump some time into this, but obviously only if you guys think this is even a viable route or worth pursuing at all.
andrew commentedon Oct 2, 2020
@brunobeltran lots of people have asked for that feature before, so it would be well received.
It shouldn't be to hard to hook up, the main thing you'd need to do is make fake notifications (because they don't exist on GitHub but we want them to show up in the API) for each of your own PRs, which then may get merged with a real notification if someone else comments on your PRs so you don't have duplicates.
brunobeltran commentedon Oct 21, 2020
Update: advisor suddenly wants me to graduate this quarter, so I won't be able to deal with this one myself. But if it's still around after Christmas, I'll definitely get this working, as it's basically preventing me from using octobox as my one-stop-shop and I love this tool.