GitHub

What you can do

Ask Zanbase Agent to create a GitHub issue from work you describe in chat. Supply the repository owner, repository name and issue title, with a body when needed. The action queues the issue creation and returns a job identifier.

For an existing issue, supply its number, repository and the comment to post. Automations can run the same create-issue and comment actions as configured steps. For example, a rule can post a specified update to a known issue when its trigger fires. This connection exposes those write actions; it does not add a repository browser or synchronize issue status with Zanbase tasks.

Permissions and privacy

A workspace admin authorizes the GitHub connection for the whole workspace. The connection requests GitHub’s repo permission. Zanbase stores the connected account’s identifier, label and granted permissions, and encrypts its stored access and refresh tokens.

A workspace admin can open Settings, then Connected apps, select Disconnect beside the GitHub account under Connected accounts, and confirm Disconnect. If the result says the provider grant could not be withdrawn, remove it in GitHub account settings too.

Good to know

In chat, approve the requested action before it runs. For recurring work, create an automation and review its repository, issue number and message before enabling it.

Capabilities and permissions

• Writes: Create GitHub issues with a title and optional body through Zanbase Agent and automations. A workspace admin connects the workspace account.
• Writes: Post comments on GitHub issues through Zanbase Agent and automations. A workspace admin connects the workspace account.

Setup

Products used

• Zanbase Agent
• Automations
• Projects