Find, filter, open Git repositories

[deanishe 891]

I'll look into it, but it could potentially slow the workflow down a lot: it'd have to read each alfred-repos.json file before sending the results to Alfred, otherwise the subtitles would be incorrect.

[Maddog 2]

I think it's ok to just have it as part of the update process, read the directories and custom editor assignments.

[deanishe 891]

That's doable, but require a much more significant rewrite. Still, definitely seems like a very useful feature, so probably worth the effort.

[Maddog 2]

Thanks! Of all the workflows I've written, this is the one I use the most personally.

 

Many months later, this has also become my most used workflow, I run "update repos" the second I run "git init". Really love it.

 

However, funnily, without fail I always forget the hit modifier keys and open projects in the wrong IDE. When I need console or finder, I always remember, but the multiple IDEs are merged in my mind

[deanishe 891]

Updated with some Alfred 3 goodness.

• Now auto-reloads results when an update completes
• Auto-updates list of repos when settings have changed
• Better handing of remote/origin URLs
  • Can handle more URLs (not just GitHub and Bitbucket)
  • Add "meta" app `Browser`, which will open the URL in your default browser
• Clearer naming of applications in settings: app_1 -> app_default, app_2 -> app_cmd etc.

[Maddog 2]

I can't get rid of the new version line, it says 2.1.1 is available, I tried hitting enter on that line but nothing happened (also nothing happens in debugger at the point of clicking)

 

I tried updating from github releases, but still showing that line.

[deanishe 891]

I made a silly error. Grab v2.1.2.

[Maddog 2]

Still same problem. I even restarted Alfred in case it was cached.

 

Shows 2.1.2 under Alfred preferences, but when I call "repos", I still see "Version v2.1.1 is available" as one of the items in the list.

 

[deanishe 891]

Try repos workflow:delcache to reset the cached list of versions.

[Maddog 2]

That did it.

Thank you!

[Maddog 2]

@deanishe Have you considered adding fuzzy matching to this workflow one day?

[deanishe 891]

Yes. One day.

[Maddog 2]

@deanishe I can't make exclude work, I tried these with and without an asterisk:

  "global_exclude_patterns": [
    "node_modules/*"
  ],          

and

"search_dirs": [
  {
    "depth": 5, 
    "name_for_parent": 1, 
    "path": "~/Code"
    "excludes": [
      "node_modules/*"
    ]
  }
]

I see one repo (a library I'm working on) showing up 4 times in the results, once for the original location and 3 times inside other projects /node_modules/ folders.

 

What am I doing wrong?

Thanks

[deanishe 891]

55 minutes ago, Maddog said:

What am I doing wrong?

 

depth=5 would be the obvious problem.

[Maddog 2]

9 hours ago, deanishe said:

depth=5 would be the obvious problem.

 

So exclude doesn't work with depth? Not all my repos are directly under ~/Code, some are deeper, is there a way to include them in the search but exclude node_modules?

[deanishe 891]

exclude works fine with depth. depth=5 is in itself not ideal because you will end up searching a lot of directories.

 

Try “*/node_modules/*”.

[Maddog 2]

11 hours ago, deanishe said:

Try “*/node_modules/*”.

 

Thank you, that worked.

[somewhere2go 0]

The select repository does not open with Atom application.

 

Thanks in advance.

[deanishe 891]

On 18/03/2018 at 8:29 PM, somewhere2go said:

The select repository does not open with Atom application.

 

Works perfectly for me. The workflow's behaviour is entirely dependent on your settings file, so could you post the relevant parts on here, please?

 

Enter "reposettings" in Alfred to open your settings.json file.

[somewhere2go 0]

Quote

Works perfectly for me. The workflow's behaviour is entirely dependent on your settings file, so could you post the relevant parts on here, please?

 

Enter "reposettings" in Alfred to open your settings.json file.

 

Thanks, now it works perfectly. Maybe for my mistake in the script.

[Wietse 0]

I keep getting: not a Version instance: None

What am I doing wrong?

[Maddog 2]

@deanishe - I'm wondering, how does this workflow search for the app which we pass in the config?

 

I've been having issues forever with VSCode where right after it updates (for a day or two), this plugin would open the wrong VSCode and not the one from /Applications.

I tried setting the full path in the config and it seem to have solved the problem, but I'm wondering how it works, because I think I'm having similar issues with other editors as well (which could be in ~/Downloads AND in /Applications).

[deanishe 891]

TL;DR: Put your apps in /Applications or ~/Applications. Otherwise, you'll have problems sooner or later.

 

1 hour ago, Maddog said:

how does this workflow search for the app which we pass in the config

 

It doesn't. It delegates opening stuff to the OS by calling open -a AppName /path/to/repo.

 

1 hour ago, Maddog said:

I think I'm having similar issues with other editors as well (which could be in ~/Downloads AND in /Applications)

 

In my experience, the bottom line is that if the application isn't in /Applications or ~/Applications, you're likely to have issues with it sooner or later.

 

It can cause problems simply having different versions of the same application installed (e.g. Alfred 2 and Alfred 3 cause conflicts). Multiple copies of the same version is a total crapshoot.

 

1 hour ago, Maddog said:

I tried setting the full path

 

But that should work.

 

All the same, it's safest to put your apps in /Applications or ~/Applications, and delete any other copies of the same app.

 

Edited July 5, 2018 by deanishe

[Maddog 2]

2 hours ago, deanishe said:

All the same, it's safest to put your apps in /Applications or ~/Applications, and delete any other copies of the same app.

 

The update process for VSCode is putting some version (not sure if it's the new one or the old one) under /Library/Caches and for at least a couple of days after the update, I'd randomly get either the old or the new version. It's out of my control unfortunately. Hopefully now that I have the full path it won't happen anymore.

 

Thanks for the tip, I moved my other editor out of ~/Downloads.