How can I search an issue on GitHub that contains keywords "java" AND ("python" OR "C++")? Is it possible to represent a search with these logical operators like OR/AND?
It turns out GitHub does not provide functions to achieve the searching logics like ANR/OR. The solution I figured out is to write a crawler that implements the searching logics.
Well, GitHub does not work like StackOverflow, but there are some ways to achieve what you want to accomplish. Start by using the type label, like this type:issue, then you can use the in qualifier, like this python in:title,body, which will search titles that contain the word python. Here is a more detailed (reference) of GitHub's Docs, which might help you with your issue.
I hope this helps you, but as much as I searched I could not find conditional search features on GitHub's search, but there are some pretty useful labels (qualifiers) that you can benefit from.
Github search example
I want to search these repositories which's title contain 'keyword-1' or 'keyword-2' or 'keyword-3'.
I have read the Github search help documents and search api documents, But I still have no idea how to search with multiple keywords.
Thanks.
I think the best way to do that is the way you are demonstrating. I mean just use the tags separated by simple space. I have just tested that the first repositories that are shown are those containing all the tags that I am searching. Give it a try, it must be working just fine
for now you can use curl and jq to achieve this. Check out this gist
Here is a little background on the task:
My client has a sharepoint site that has a list of data. One of the columns or fields is a date field, this date is entered manually using MM/DD/YY Format.
My client has requested me to add an option where they could filter the columns by a range of dates on the webpart view.
I read this guide: https://www.nothingbutsharepoint.com/sites/eusp/pages/sharepoint-list-filtering-by-date-range.aspx and i got it to work, but it seems to be a bit buggy, meaning that sometimes the list will not get filtered by the specified dates..
Another issue with this method is that there is no Submit/Go button.
FROM: [ Text Field ] TO: [ Text Field ] [GO Button]
My client would love to have something like the example above where there are two text fields next to each other and a button that they can click to make the filter activate.
I searched for hours and hours and was not able to find something like this.
Do you guys know of a solution and if so, provide me with a link or guide, on how to achieve this problem? Thanks
EDIT:
It seems that there is a Apply Filters Button Web Part that does what i need. I added it and it seems to work Okay. I have to click Apply Filters TWICE in order for it to work.. weird huh? is there a fix for that?
FYI: i followed the guide linked above and just added the apply filters button.
Okay i fixed it,
It was because i was adding the date filter web parts to the library itself, and i was supposed to create a page for it and add my web-parts in there.
Found a solution that'll load the filters on first click for me.
In SPD, under the web part that displays the list items (XsltListViewWebPart), change these two to "True":
ClientRender="True" and IsClientRender="True"
Similar issues mentioned in this thread gave insights to button load sequences and why it doesn't render results on the first click.
I'd like to add a new column in a Github issues report with the date when a specific label was added for the first time. Checking at the Issue Labels API on Github, I see no way of achieving this, as Label entities don't contain dates.
Is there another way to find out when a label was set to an issue?
No, there isn't currently a way to do this. The nearest thing would be the updated_at entry on an issue, but there's no way to guarantee that that update was the result of a label being set on the issue.
GitHub clearly has this information, as the timestamp from a label being applied is available in the web UI—I wonder if you might be better off scraping the page (and asking GitHub to provide this information via the API)?
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