fix(filter): `repo:foo/bar` doesn't apply to the section

[davinkevin]

Hi 👋

I just started using this project for my own management and I discovered the repo:gradle/dv filter doesn't work/apply.

If I set a section with a filter, every PR still shows up. It's the same if I put an imaginary and non existing repo, like repo:foo/bar (which should display nothing IIUC).

Thank you

[pvcnt]

Hi @davinkevin! Could you please share the exact configuration of your section? I experimented with the following queries: repo:apache/solr and repo:apache/solr involves:@me and both showed me what I was expecting. Also, could you please confirm that your Personal Access Token has access to this repository?

[davinkevin]

My configuration looks like this:

Panel query: is:open is:pr "This PR has been generated by Renovate Bot" repo:foo/bar

My connection configuration:

• api: https://api.github.com
• filter organization: foo

Even if I've modified my org by foo and the repo I would like to focus with bar, you can see I have another called bar-support (the pattern is the same, I just replaced the name).

[pvcnt]

Ok, I see, it looks like specifying both org: (implicitly added via the org filter in the connection specification) and repo: does not work as expected, with the latter being ignored. I can provide a fix for this edge case.

Unrelated question, but seizing the opportunity to know how people use this project: how is it deployed? Docker, Helm, static build, other?

[davinkevin]

I use the helm version (even if as an ops I don't like helm 😅), and it's deployed using GitOps here

[pvcnt]

It should be fixed by now! Could you please confirm, if you have the opportunity to?

And I'm glad you're using the Helm deployment. I will shortly move to a more traditional client/server model (because having only an SPA is too limited), but anyone relying on the Docker image or Helm Chart should be able to upgrade seemlessly.

[davinkevin]

It's working!

I have just two, not three!

Thx!