Closed ejholmes closed 5 years ago
For legacy reasons, slashdeploy.io uses a client_id/client_secret from a GitHub OAuth app instead of the client_id/client_secret from the GitHub App.
GitHub apps now support all of the API calls that SlashDeploy uses, which means we can switch the client_id/client_secret over to the GitHub app.
This PR adds a rake task that will request all users to re-authenticate with GitHub so that we can eventually remove the legacy OAuth app.
For legacy reasons, slashdeploy.io uses a client_id/client_secret from a GitHub OAuth app instead of the client_id/client_secret from the GitHub App.
GitHub apps now support all of the API calls that SlashDeploy uses, which means we can switch the client_id/client_secret over to the GitHub app.
This PR adds a rake task that will request all users to re-authenticate with GitHub so that we can eventually remove the legacy OAuth app.