Update github-integration.adoc

[e-grapp]

Description

A brief description of the changes.

Add a mention of Env Vars for write access since we mention SSH keys and no mentions of permissions needed elsewhere

Reasons

A link to a GitHub and/or JIRA issue (if applicable).

User wrote in about this in a ticket
https://circleci.zendesk.com/agent/tickets/140038

Content Checklist

Please follow our style when contributing to CircleCI docs. Our style guide is here: https://circleci.com/docs/style/style-guide-overview.

Please take a moment to check through the following items when submitting your PR (this is just a guide so will not be relevant for all PRs) 😸:

• Break up walls of text by adding paragraph breaks.
• Consider if the content could benefit from more structure, such as lists or tables, to make it easier to consume.
• Keep the title between 20 and 70 characters.
• Consider whether the content would benefit from more subsections (h2-h6 headings) to make it easier to consume.
• Check all headings h1-h6 are in sentence case (only first letter is capitalized).
• Is there a "Next steps" section at the end of the page giving the reader a clear path to what to read next?
• Include relevant backlinks to other CircleCI docs/pages.

[rosieyohannan]

@e-grapp So my understanding is this is a list of things CircleCI can do on a user's behalf once they have these permissions. Rather than listing things the user is able to do. Maybe there's a better way to surface this 🤔 Does that make sense?

[e-grapp]

@rosieyohannan - apologies for delay on this!

Totally makes sense and I think you're correct that this isn't the best way to surface this as this is more of what CircleCI can do on behalf of user

We have an equivalent for Apps/GL but not exactly for OAuth integrations and I'm thinking an equivalent would be the best approach for this:

https://circleci.com/docs/roles-and-permissions-overview/

[rosieyohannan]

Oh interesting! Thanks, I'll turn this into a Jira and then close the PR