RevellNL

Github workflow for Alfred v2
A configurable workflow for Alfred v2.

Installation
You can install this workflow by dowloading the Github.alfredworkflow file and either double-clicking it, or dragging it onto the Alfred Workflow screen.
After adding it to your workflow collection, when you run the gh command in Alfred you will be presented with only two options; auth and token.

First, you'll need to choose for the auth option, this will generate an OAuth token for you which will be used by all subsequent calls to the Github API.
Once you get the OAuth token, copy it from the website, run gh token and paste the OAuth token in the Alfred window.
gh token thisisthetokenwhichcamefromthewebsite  
Now you're all set to start using this workflow!
 
Usage
The initial command for starting this workflow is gh.
The commands currently supported by this workflow are:
repo
This returns a list of options for listing your repositories  You can filter the results show by typing (part of) the repositoryname after the workflow command, f.e.: 
 
If there's anything you run into which isn't working as you expect, or not working at all for some reason. Please, do let me know!
 
Also, be sure to check out the repository and maybe make some additions yourself!

No sir, that's why a folder outside of the actual workflow folder is recommended to be used.

When you have two commands (“gh” and “gh_auth”) people will constantly see the auth command when wanting to do the other, which in my view adds some unnecessary visual clutter (seeing as it’s a command that’ll only be run once).

I’d make a suggestion, which is similar to what I’ve implemented on PinAdd — make it an action modifier

It can still be seen as a security risk (albeit only in very specific cases). Since it’s saved in plaintext, someone can still snoop around (not to mention it’ll probably be uploaded do Dropbox).
Maybe there’s an easy way to do it via OAuth.

Github workflow for Alfred v2
A configurable workflow for Alfred v2.

Installation
You can install this workflow by dowloading the Github.alfredworkflow file and either double-clicking it, or dragging it onto the Alfred Workflow screen.
After adding it to your workflow collection, when you run the gh command in Alfred you will be presented with only two options; auth and token.

First, you'll need to choose for the auth option, this will generate an OAuth token for you which will be used by all subsequent calls to the Github API.
Once you get the OAuth token, copy it from the website, run gh token and paste the OAuth token in the Alfred window.
gh token thisisthetokenwhichcamefromthewebsite  
Now you're all set to start using this workflow!
 
Usage
The initial command for starting this workflow is gh.
The commands currently supported by this workflow are:
repo
This returns a list of options for listing your repositories  You can filter the results show by typing (part of) the repositoryname after the workflow command, f.e.: 
 
If there's anything you run into which isn't working as you expect, or not working at all for some reason. Please, do let me know!
 
Also, be sure to check out the repository and maybe make some additions yourself!

Ours also requires and Basic seemed to do the trick for me.
 
Just set your url to http://USERNAME:PASSWORD@jenkins.url/
 
EDIT:
 
Just realized you were using google creds.  Might be able to still get by with this. Or maybe a one time use password if you are using two factor.

Hi all,
 
I've created a workflow for interacting with a Jenkins CI instance. Currently it only supports fetching the status of the builds but I'm planning on expanding this to getting the health of the builds, starting builds and some other neat features.
 
You can download it from here, or you can check out the GitHub repository here.
 
When you've installed it in Alfred, be sure to set the correct URL to your Jenkins CI instance via:
Alfred > Preferences > Workflows > Jenkins > Script Filter And then entering the correct URL in the "Script" box.
 
Be sure to let me know (either here or on GitHub) if you run into any issues, or if you have any ideas!
 
 

* project names and statuses added for illustrative purposes