Hey, thanks for the PR :)
I'm wondering, is there ever a reason to search for prs/issues on archived repos?
Like, what if you're the one that archived the repo, maybe you still like to see prs/issues?
I need to read about what an archived repo actually means.
If we add the is:archived filter, users aren't aware, as the search bar shows just is:pr.
Now I'm not a fan of also showing archived:false as it takes up too much space but we can add a note in the docs site.

Hey, thanks for the PR :) I'm wondering, is there ever a reason to search for prs/issues on archived repos? Like, what if you're the one that archived the repo, maybe you still like to see prs/issues? I need to read about what an archived repo actually means. If we add the is:archived filter, users aren't aware, as the search bar shows just is:pr. Now I'm not a fan of also showing archived:false as it takes up too much space but we can add a note in the docs site.

I had a similar debate, but made the assumption based on prior work. Archived repos are view-only. When I figured out why there was a difference, I couldn't even close the old PR.

By default I would expect behavior to match that of GitHub's search. Considering the feature set of gh-dash, "view and take action" I like customizing the behavior to exclude archived repos since they aren't actionable. I could always view those items in GitHub UI if I really wanted to.

I'm happy to change behavior and/or update docs! But will wait for your opinion, I'm just a lowly user 😂 .

ok cool makes sense. Let's just add a disclaimer in the docs