How do you keep track of your comments in issues on GitHub?

Github

Github Problem Overview


I want to easily find all issues I've commented on in GitHub.

I've tried searching commenter:mbigras type:issue as per the recommendation from the GitHub Help for Searching Issues.

However, that method returns fewer results than the public activity section of my profile.

See both attached images:

Search method

Doesn't display current results: enter image description here

Profile method

Gets mixed up with other public activity: enter image description here

Is there a way to get the full history of my comments on GitHub?

EDIT

author:mbigras type:issue gives wider results but still not the full history: enter image description here

What I'm looking for is a way to quickly view all my comment/issue history in all issues.

EDIT

I emailed GitHub about this. Search doesn't match the public activity section because search indexes issues by creation date and not last active date.

How do you keep organized about which issues you've commented on?

Github Solutions


Solution 1 - Github

Search for commenter:username in the main Github search box.

For example commenter:gavinandresen

To see recent activity, select Recently updated from Sort dropdown

You can also narrow the search: is:issue commenter:gavinandresen

enter image description here

Solution 2 - Github

I have also been very frustrated when I could not find an issue that I have commented on a while ago. I even did not remember the project it was in. I knew only the problem I was referring to.

Then, I went to the Notification settings on Github and saw there is an Include your own updates option that is unchecked by default.

Include your own updates

Once you check it, Github will send you an e-mail notification about every comment or PR you make. They you probably want to add an appropriate label and filter for emails so Github messages do not clutter an inbox.

My life has changed since then. Now, every time I want to find something I have written on Github, I just search for it in the e-mail notifications.

Solution 3 - Github

You can view all the issues on Github you have commented on by going to https://github.com/notifications/subscriptions and selecting Reason as Comment.

This will show all the issues that you've commented on.

You can also filter the issues by selecting other reason such as Assign, Author, Manual, Mention, etc. but you can select only one reason at a time. Also, you can filter the issues by repository by selecting the concerned repository from dropdown after clicking Repository

Solution 4 - Github

This might be a little late, but there's also another way to find what issues/PRs you have participated in. This method also brings in a lot more things you might be interested in too!

When you are on the website main page, on github.com, use the keyboard shortcuts as described here to open your pull requests or issues. The shortcut for these is in particular [g, i] for issues and [g, p] for pull requests (I remember g by go, but whatever works for you.)

After you go to the page directed by these shortcuts you are greeted by an entire screen of goodies you can use! The search bar can be edited and the buttons can be used to make your experience fast!

pr-display-github

Solution 5 - Github

Search All GitHub using the search term is:issue author:@me

enter image description here

You can also check the following links.

For all your subscriptions https://github.com/notifications/subscriptions

For all your issues https://github.com/issues

For all your pull requests https://github.com/pulls

In case someone is interested to know how to find these links, go to github's resi api documentation. The URL's are not explicitly described there. However, look for the page names bellow REFERENCE.

enter image description here

If you lowercase the relevant word (for example Issues become issues, Pulls become pulls) and put that after https://github.com/, you most probably will find what you are looking for.

Solution 6 - Github

Also, since Github is on the web, any HTTP search engine works, eg Google, Bing, etc. This works to the extent of your search engine's quality and the uniqueness of the writer name.

(Indeed, I actually do this all the time when I need to find any previously written web (engine)-accessible publication, including those on StackExchange. Names I use are 1 in probably an infinity, so Google often works better than forum search options.)

(Sample Google link.)

Solution 7 - Github

If you want to search for multiple users in a single search, use it like in the global search bar without the OR logical conjugation:

commenter:FantomX1 commenter:FantomX1-github

since the similar google way approach with 'OR' would not work

commenter:FantomX1 OR commenter:FantomX1-github

Solution 8 - Github

Type involves:<your username> in the search box on the GitHub's main page. This will find all the issues that you commented on, was assigned to or mentioned in.

For example, if your username on GitHub is unclebob, the search query should look like:
involves:unclebob
Or if you're logged in to GitHub, then simply:
involves:@me

Note the difference between involves and similar search qualifiers - author and commenter:

  • author will find only the issues that were started by you; if you comment on the issue that was started by someone else, author query won't return it in the search results.
    E.g., compare involves:unclebob and author:unclebob type:issue.

  • commenter will find only those issues where you commented second or later (creator of the first comment in an issue is considered its author and not a commenter); if you start an issue and then never comment on it, the commenter query won't return it in the search results.
    E.g., compare involves:unclebob and commenter:unclebob.

In other words, when it comes to searching comments, author and commenter return only a subset of involves' results. So I recommend using involves not to miss anything.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionmbigrasView Question on Stackoverflow
Solution 1 - GithubToolkitView Answer on Stackoverflow
Solution 2 - GithubfraczView Answer on Stackoverflow
Solution 3 - GithubRounakView Answer on Stackoverflow
Solution 4 - GithubIsham MahajanView Answer on Stackoverflow
Solution 5 - GithubAhmad IsmailView Answer on Stackoverflow
Solution 6 - GithubPacerierView Answer on Stackoverflow
Solution 7 - GithubFantomX1View Answer on Stackoverflow
Solution 8 - GithubA. MiltoView Answer on Stackoverflow