pr for issue #57

what i have done

hosted a cors-anywhere proxy, used that link for github Oauth this way login in works
created an input component with submit button to for creating and submitting components
- submit buttons becomes active once input text-area becomes dirty
- editor can detect markdown (still a bit buggy, markdown strings aren't properly formatted if the comment in markdown syntax is to big)
create a gql query for querying the most recent comment
- for updating the comments once the new comment is mutated with githubgql on issue
create a mutation (update) query for adding a comment to an issue

would it be an idea to host the website somewhere like vercel, this way the sensitive information regarding oauth can be injected through an .env file (atm sensitive information is layed bare)
I think we need to add in the documentation a few lines on how to host your own cors-anywhere proxy and update the authenticate function in GithubCallBack.js to reflect this change.
the github app should also be granted permissions to read metadata (I had to include this is order for issues on my repositories to show on the website)