I want to find all the GitHub issues that I commented on. I tried searching for commenter:mbigras type:issue like the Searching issues and pull requests GitHub article suggests. But that method returns fewer results than the public activity section of my profile.
See both attached images:
Search method
Doesn't display current results:
Profile method
Gets mixed up with other public activity:
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:
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?
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
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.
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.
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
Search All GitHub using the search term is:issue author:#me
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.
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.
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!
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.
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.)
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
I plugged in the Google Custom Search Engine to my MediaWiki site. It seems to work fine. However, how do I also make it search for results using partial matching? For example: when I searched for 'loft', it returned only the pages containing the whole word 'loft', but I was also looking for the pages containing 'loft' as a substring of some words, like 'createloft', 'deleteloft', 'loftstudy', etc.
Google doesn't provide such advanced search features. If you need things like per-namespace search, substring matching, regex search etc. use CirrusSearch, which is based on ElasticSearch.
My question is simple, how do I make a certain page be find-able by a specific keyword.
cse it's working fine it just don't manage to find everything he supposed to.
Google custom works like google search, manipulating results may not be possible, however, check out the synonyms tab in google.com/cse.
Say your users search for MBA you can configure it to show results for Master of Business Administration
Is it possible to make a shorter keyword for the users to access our opensearch?
Example:
Our website is: xxxxxxxxx.com
I want that when typing 'xxx' and pressing TAB the opensearch for our website will appear.
Right now the users have to type the whole address and then press TAB.
It is not possible to make keyword shorter, if you search is on xxxxxxxxx.com, keyword is xxxxxxxxx.com, you can't do with it anything.
Nevertheless you probably also don't have any problem.
Google Chrome behaviour is as follows:
User visits site with opensearch link. Google Chrome plug this search engine, and then when you start typing first x into location bar, xxx engine is offered with pressing TAB key.
You probably did something wrong, when you was testing it (and didn't post here infos about it).
Because when you add manually new search engine, you need first at least once visit site, engine belongs it. Otherwise you must type whole xxxxxx.com.
Is there a way to search for text in the documentation pane of Eclipse?
E.g. see the attached screenshot showing some Android SDK documentation:
and see this screenshot showing the Search menu:
I can't see how you can do a search. And Cmd F doesn't seem to do anything either.
This is basically a web browser pane. Sadly it is quite limited in functionality, you can't search within the view (and of course not within the documentation database instead of the currently shown document).
So the work around is to open the document in a complete, external browser. In this case it is easy to find the document (http://developer.android.com/reference/packages.html) but sometimes it might be annoying to find the URL as this limited web browser view doesn't even tell it to you or gives you a possibility to get it.
If it was about site search and not searching withing the page and if the site doesn't offer a site search (this one does) then of course you can use Google with a site:developer.android.com parameter; similar for other search engines.