How are GitHub permissions handled?
The GitHub connector checks pull requests, issues, and CI within the permissions of the connected GitHub account.

What is moving forward, and what still needs attention? In INARY you ask the AI about GitHub, review the situation with your team, and request an issue or the next action right there.
Engineers are not the only people who need to know where development stands. Sales wants the release date, management wants the reason for the delay, support wants the status of a bug. But GitHub means nothing to anyone outside engineering. So every "how is that going?" lands on an engineer, and development stops each time they answer.
With INARY's GitHub connector, you ask the AI about pull requests, issues, and CI. "Which PRs were merged this week?" "Which open issues are high priority?" "Where is CI failing?" The AI looks at GitHub and answers in plain language. The situation gets put into words without an engineer re-explaining it.
The answer appears in the thread, so people outside engineering read it in the same place. Sales checks the release timing, management reads the reason for the delay, support sees the status of the fix. When the team decides that a bug becomes an issue to handle this week, you request the issue creation or the next action from the AI right there. Review and action happen in the same place.
Fewer "how is that going?" interruptions, so development stops less often. Non-engineers check the status themselves, so decisions come faster. The history of the work stays in the thread, and people who join later can catch up.
The GitHub connector checks pull requests, issues, and CI within the permissions of the connected GitHub account.
Actions such as creating an issue are requested from the AI after the team has reviewed the situation in the thread. Who requested what stays in the thread.
The current connector is GitHub. See the connectors page for the full list.