jenkins_api_client VS Octokit

Unfortunately the gem jenkins_api_client uses net-http library directly https://github.com/arangamani/jenkins_api_client/blob/c59970e8530e1e2caa0db3bdec70d1f09e8750b2/lib/jenkins_api_client/client.rb#L423 . This does not allow easy customization.

After extracting the GitHub username from the Paddle payload, I would use the octokit gem to add the customer as a read-only collaborator to the repo. Something like this:

Some important things in this reflex. One, since our partial requires a form object, we use ActionView::Helpers::FormBuilder to create a form for a user building an initial repository. Since it requires a view_context, we leverage a delegate to access it from the controller. Two, the Octokit client requires a user authentication token, so we add delegate to the connection so we can access the current_user. Three, rather than triggering a full page morph, we instead can use a selector morph so it only updates the div with id #repositories.

Here's an example of doing that on octokit gem: https://github.com/octokit/octokit.rb#debugging