ProLoser / Github-Omnibox

Github Commands from Google Chrome Omnibox (address bar)
http://goo.gl/n5HJw
MIT License
386 stars 24 forks source link

Quicker way to get to often visited repos? #64

Open janpio opened 7 years ago

janpio commented 7 years ago

I am active in two orgs and have an additional one myself. Is there a quicker way to get to their repos than to type their full name followed by slash and then the repo name?

I visit those orgs and repos quite often, so maybe the extension could pick that up somehow? (I am only a member of 2 of these orgs, the other I am just a random user)

janpio commented 7 years ago

(Starring all the relevant repos and using gh *reponame might be a workaround)

ProLoser commented 7 years ago

/ only should give you all repos you have write access to but it's been a while so I don't remember.

So org/whatever will show up if you type "/wh"

On Fri, Oct 13, 2017 at 5:59 AM Jan Piotrowski notifications@github.com wrote:

(Starring all the relevant repos and using gh *reponame might be a workaround)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ProLoser/Github-Omnibox/issues/64#issuecomment-336445635, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEHQ9Dmxo879Kjaq2piQKi7qxR_dzGOks5sr17JgaJpZM4P4cvS .

janpio commented 7 years ago

Ok, my own org is covered. Unfortunately I don't have write access on the others.

Does the extension know locally about any of my e.g. issues that could be used to automate searches in some orgs that I visit often?

Does gh / correspond to an API endpoint or would it be possible to add a list of "consider these orgs as mine as well" option in the settings?

ProLoser commented 7 years ago

All this logic is in the extension mostly. I just query stuff and cache it locally and then search the caches.

If you can follow an org it may show up when you use @ but I don't think GitHub let's you follow orgs (sadly). The flow you described which would be fine entirely through the extension doesn't feel very good (I prefer using information already in GitHub and just applying sensible logic to it).

One way to get where you're going faster might be to have a bigger reliance on frequency and history. Repos you select within the extension more frequently get higher priority.

I feel like if this work got polished and finished it might do what you want https://github.com/ProLoser/Github-Omnibox/pull/49

It essentially is like combining all the caches during searching so you don't have to use special triggers like ! / @ *

janpio commented 7 years ago

Yeah, no follow for orgs :/

Hm yeah, #49 would probably work in some way - but that is a major change. I was hoping for a small, little thing to cover my usecase ;)

ProLoser commented 3 years ago

I came up with a new version of this project I think you would like.

It should monitor any repos you can push to, starred or watch. Then whenever you search it will show a filtered list of results from those. I think I'm going to remove all the UI tweaks and shortcuts since they are all integrated.