WIP comments
We probably don't need `public_repo` scope
More WIP changes
First stab at arguments for Devise initializer
Fix options format
Confirming the Omniauth setup-phase approach.

Now we just need to work out how to set up the values properly. I might wind up just rewriting most of the options hash.
Pinning the Devise version, for safety
variable in setup block overrides policy
Finishing up authentication configuration
Users can produce a list of previous auth portals.

By querying Runs and any residual Authorizations.
Extract auth_provider as a class method
Should be enough to accept users from any portal.
Allow logins to choose the portal to auth with.

This should be the last piece of [#55550912]. If a user goes to the sign-in page ( /users/sign_in/ ) the login form and registration links are now hidden, and instead there's a row of links to configured portals to authorize with. (The register/sign-in forms are still available in development.) These links each have a parameter which designates which portal to use for authentication. (Actually the parameter designates an entry in a hash of allowable portals.) The Omniauth strategy then authenticates with the correct portal.

https://www.pivotaltracker.com/story/show/55550912
Merge branch 'refs/heads/multi-portal-auth'
Login path links to account picker
Reads portal configuration from YAML [#55550912].

This version is flat, to deliver just the name => url mapping. The next step will be to provide more data per configuration. Note that the keys are now strings, not symbols, throughout. (Also note that when we have more data, this YAML file will get moved into a "sample" and the real one will be deployed via Chef.)

https://www.pivotaltracker.com/story/show/55550912
More-structured portal configuration in YAML.

This allows stowing image URLs and portal client secrets along with the URLS, which will happen when we start publishing to these portals.
Use images in the auth selection page, if provided.
Add interactions staging for testing/demo.