Added OAuth hash for testing Github provider

[SidharthBansal]

I have created auth hash for testing of Github provider. This is part of #2676 issue's Github provider subissue

[plotsbot]

	1 Warning
⚠️	It looks like you merged from master in this pull request. Please rebase to get rid of the merge commits – you may want to rewind the master branch and rebase instead of merging in from master, which can cause problems when accepting new code!

	1 Message
📖	@SidharthBansal Thank you for your pull request! I’m here to help with some tips and recommendations. Please take a look at the list provided and help us review and accept your contribution! And don’t be discouraged if you see errors – we’re here to help.

Generated by 🚫 Danger

[SidharthBansal]

@jywarren can you please review the changes? This is ready.
@jywarren I want to know whether I should start working on Bootstrap Upgrade along with the OAuth OR shall I wait until we are done with OAUTH.
I am eager to learn more about bootstrap but managing both projects simultaneously may be difficult.
I will do whatsoever seems best to you.
Thanks

[jywarren]

I think let's try to get this all wrapped up and debugged. I'll make time early this week to go through the setup steps for the additional OAuth systems. In the meantime if you have nothing on your hands, perhaps you could tackle some smaller issues, like tests, codeClimate, things like that? I'd really appreciate it.

Perhaps especially the persistent issue we're seeing with tests not completing properly and needing to be restarted? #2824 i think...

Merging this! Very exciting!

[SidharthBansal]

OK, then we will move to Bootstrap once we are completely done with OAuth. I have found MANY bugs at publiclab.org. Will you mind if I will create issues for all of them?
I will send patches to some of the issues as well.
I will see the Travis for sure. I want to work on Account Deletion feature. It fascinated me a lot.

[SidharthBansal]

I am right now working on tests for Github Provider

[jywarren]

I think if you have a very big list, you could start with a kind of planning issue from which you gradually break out new issues. That way it doesn't flood the issue tracker all at once? Great, thank you!!!!

…

On Mon, Jun 25, 2018 at 6:19 PM Sidharth Bansal ***@***.***> wrote: I am right now working on tests for Github Provider — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#2874 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABfJwBkHel40MVpI2cjjswVds7xm17Yks5uAWHlgaJpZM4UwAzP> .

[SidharthBansal]

Do we need still RuboCop Continuous Integration as listed in #2814 (comment)? If yes, I am happy to work on this too. I will create an issue for this one.

[SidharthBansal]

OR were you referring to do the rubocop changes?

[jywarren]

I think the idea was to see if we can get Rubocop to offer to automatically fix formatting for us. @siaw23 has mentioned this is possible. Let's open an issue and collect information?

…

On Mon, Jun 25, 2018 at 6:52 PM Sidharth Bansal ***@***.***> wrote: OR were you referring to do the rubocop changes? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#2874 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABfJ9e014ov5nO6Uel6A9t3gAWn1fCOks5uAWl7gaJpZM4UwAzP> .

[SidharthBansal]

Opening a new issue
Thanks