New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can I negate a set of search terms? #1448

Closed
tripleee opened this Issue Jan 11, 2019 · 7 comments

Comments

Projects
None yet
3 participants
@tripleee
Copy link
Contributor

tripleee commented Jan 11, 2019

Summary of Problem

I participate in a project which receives a lot of routine PRs which are usually quickly handled. I would like to exclude those by default.

  • What are you trying to do?

I want to exclude a set of issues which can be isolated with the search

repo:charcoal-se/smokedetector type:pull_request

Incidentally, if I add state:merged or state:closed the list is empty; why is that?

Ideally, I would like to add state:merged and also reason:subscribed if that's the only reason I am notified -- but I could be pinged because I am subscribed and pinged, can't I?

So naively something like

inbox:true -(repo:charcoal-se/smokedetector type:pull_request state:merged -reason:subscribed)
  • What happens?

The syntax I am imagine should exist apparently doesn't exist. Perhaps I am overlooking something in the documentation.

  • What should have happened?

Steps to Reproduce the Issue

In the broadest terms, try to filter out only the most prevalent category of issues from your inbox.

Versions, Operating System and Hardware

  • Which version/commit of Octobox are you using?

It doesn't seem to identify itself clearly; whatever is currently running on octobox.io

As of right now, the latest commit on master is df97b99

  • Which browser are you accessing Octobox with?

Google Chrome Version 71.0.3578.98 (Official Build) (64-bit)

  • Windows? Linux? Mac?

MacOS High Sierra

  • How are you deploying Octobox (Docker, Heroku, Openshift, etc)

I'm not.

@andrew

This comment has been minimized.

Copy link
Member

andrew commented Jan 11, 2019

As mentioned in the search docs:

Some prefixes also can be negated to exclude certain types of results, for example:
"-repo:splitrb/split -type:commit -owner:octobox -reason:mention".

So I think you could do:

inbox:true -repo:charcoal-se/smokedetector -type:pull_request -state:merged reason:subscribed

@andrew andrew added the question label Jan 11, 2019

@tripleee

This comment has been minimized.

Copy link
Contributor

tripleee commented Jan 14, 2019

I don't want to exclude all pull requests, or all merged tickets. I want to exclude the merged PRs which are in the SmokeDetector repo, ideally which contain ": watch" in the title, and even more ideally which are successfully merged with the originating branch deleted.

I was hoping parentheses would allow me to do a grouping like this but they don't seem to be supported, so my question is, is there another mechanism which allows me to do this?

@BenJam

This comment has been minimized.

Copy link
Contributor

BenJam commented Jan 14, 2019

inbox:true -repo:charcoal-se/smokedetector -type:pull_request -state:merged reason:subscribed watch should get you pretty close to what you're looking for. I don't believe notifications are fired from GH for branch deletions https://developer.github.com/v3/activity/notifications/#notification-reasons

@BenJam BenJam closed this Jan 14, 2019

@tripleee

This comment has been minimized.

Copy link
Contributor

tripleee commented Jan 15, 2019

That query shows me no issues at all. Removing a few of the search terms I can get a single issue e.g. with

 inbox:true -repo:charcoal-se/smokedetector -type:pull_request watch

but there should be hundreds, and the one I see actually has "watch" in the title.

I'm afraid we are not communicating clearly, but I also fail to see how to explain this more clearly. Should I open a new issue with a different wording?

I want to see all my inbox tickets except those which match a particular, complex query. I'm coming to the conclusion that there is no way to do that currently.

@andrew

This comment has been minimized.

Copy link
Member

andrew commented Jan 15, 2019

@tripleee I think I understand what you're asking for (sub-queries), and no there's currently no way to do that, all filters operate on the whole search.

@tripleee

This comment has been minimized.

Copy link
Contributor

tripleee commented Jan 16, 2019

Thanks for confirming. Should I open a wishlist ticket or do you already have something like this in your plans?

@andrew

This comment has been minimized.

Copy link
Member

andrew commented Jan 16, 2019

@tripleee opening a feature request issue would be great thanks 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment