Outstanding GitHub Items

Recently I received a bump on a GitHub pull request. This surprised me, because I was unaware of anything outstanding. I was even more surprised when I discovered that the distribution in question also had two open issues, one dating back about three months.

I have no idea why I was oblivious to these, but it made me want to audit myself to see if any other distributions had the same problem. GitHub has these nice links at the top of the page, Pull requests and Issues, but these show pull requests and issues that I initiated. I found no obvious way to display pull requests or issues filed against my repositories.

Now, maybe it is just me, but I find GitHub's documentation moderately opaque. But with considerable help from Duck Duck Go, I discovered the answer: you type into the search box is:open user:<your GitHub user name>. This gets you both open issues and open pull requests. If you want, you can restrict this further with is:issue (for issues) or is:pr (for pull requests). Do not leave off the user name, even if you are logged in. If you forget this you will get every open item on GitHub -- all 102 million of them as of this writing.

Now I am lazy, so I made a browser shortcut to do this for me. I don't think you get private repositories this way, but I was not worried about that. The string will have to be URI-escaped. So now if I want to audit myself I just click on https://github.com/search?q=user%3Atrwyant+is%3Aopen and see what I get.


I had this problem a couple years ago. I was horrified that there were issues in my repos that I'd never seen because I thought I was good at responding to them even if I didn't have a fix.

But, I guess GitHub notifications can only get you so far when you have your fingers in so many things:.

I developed this filter, where you'd have to change the GitHub username and the labels to filter out:


This should show me everything that is open and available for work. If I've applied the "stalled" label, then I've left a note in the issue about what's blocking it. Largely that's people not returning the details I need to reproduce it or no one who cares enough to fix it.

I don't think I'm missing that much now, and I try to keep that list empty. However, there are probably many stalled things I'm ignoring and have forgotten.

Certainly! I didn’t mean it as any kind of discouragement at all. I’ve just been compiling this kind of query for a while, and since you’re posting about it, I thought my collection would be of interest.

(It’s not 7 years and more detail either, btw. The 7-year-old version of that article was at about where you are at now. That it’s as detailed as it is today is due to updates over time as I’ve needed and worked out more nuance to the queries. It is my most (and most substantially) updated article, in fact.)

Hehe, oops.

I have a small script that I made (together with ETJ++'s help on the GraphQL) that finds all repositories that I have access to and finds how many open PRs they have.

This helps in my case because GitHub's search does not have a syntax to search based on permission rather than just the owner.

Leave a comment

About Tom Wyant

user-pic I blog about Perl.