--- title: GitHub Integration for TestingBot description: 'Connect GitHub to TestingBot with one-click OAuth and report bugs from any test: create or update GitHub issues with test metadata, screenshots and a link back to the test.' source_url: html: https://testingbot.com/support/integrations/github-issue-tracker md: https://testingbot.com/support/integrations/github-issue-tracker/index.md --- # GitHub Integration Enable the GitHub integration to report bugs straight from your tests: create a new GitHub issue or update an existing one, with test metadata, screenshots and a link back to the test included automatically. A **Report a bug** button appears on every test detail page, and during a Live Testing session you can file an annotated screenshot as a GitHub issue. ## Connect GitHub Go to [Members \> Integrations](https://testingbot.com/members/integrations) and click **GitHub** , then click **Connect with GitHub**. ![Connect GitHub to TestingBot](https://testingbot.com/assets/support/integrations/github/github1-9fff2c880930f5cd6c898ee2559f82484ed806a1490d10b2ed435fc6de2b6a0e.png) You will be redirected to GitHub to authorize TestingBot. We request repository access so we can create issues on your behalf, plus read access to your organizations so we can list their repositories. We never see your password, and you can revoke access at any time from your GitHub settings. Once connected, the page shows the GitHub account TestingBot is connected as. ![GitHub connected to TestingBot](https://testingbot.com/assets/support/integrations/github/github5-16412c06c62285870d9b8de3dae367bc0e16c470b426bfa12d61eb0c2aa9316d.png) Are organization repositories not showing up after connecting? Organizations with OAuth App access restrictions require an organization admin to approve the TestingBot app in the GitHub organization settings before its repositories become available. ## Report a bug Open any test from the Test Detail page. In the header you will find a **Report a bug** button. Once one or more issues are linked to the test, the same button shows the number of linked issues instead. ![Report a bug button on the test detail page](https://testingbot.com/assets/support/integrations/github/github2-24372d0c94647d17992c856a20721b63b816e9832a55161b25b4492bfec81a3e.png) Clicking the button opens a dialog. Pick the `Organization` and `Repository` you want to file the issue in, then fill in the `Title` and `Description`. The description is pre-filled with the test metadata, and both fields support GitHub Markdown. You can optionally choose an `Assignee` from the repository's collaborators, and open **More fields** to apply one or more of the repository's `Labels`. ![Create a GitHub issue from a test](https://testingbot.com/assets/support/integrations/github/github3-feda77fac3cce54e3ad19d57b673fac65b570809b64f350451b5003b058beda3.png) Click **Create issue**. The issue is created in your repository and TestingBot shows a link to view it on GitHub. The issue is also linked to the test, so teammates opening the same test can see which issues were already reported. ## Update an existing issue Already have an issue for this bug? Switch to the **Update existing issue** tab, select one of the repository's open issues from the `Issue` dropdown and write a comment. The comment is pre-filled with the test metadata and is added to the issue on GitHub. ![Update an existing GitHub issue from a test](https://testingbot.com/assets/support/integrations/github/github4-bd10bab85339f3c3de6d4a2dc208691791d3bd94fb9d6d9ad1f54a1761b27542.png) Updating an issue links it to the test as well, so the test's issue counter includes issues you commented on. ## What gets included The pre-filled description (or comment) contains a metadata block with: - The test name, linked to a shareable test page with the video, screenshots and logs - The test result (passed or failed) - The browser or device and operating system the test ran on - The error message, when the test failed with one You can edit or remove any of this before submitting. Whoever opens the issue on GitHub can follow the test link to watch the video and inspect the logs, without needing a TestingBot account. ## Live Testing During a manual Live Testing session, click **Report Bug** to take a screenshot and annotate it in the editor. Then click **Report a bug** and choose **GitHub**. The same dialog appears; the annotated screenshot is uploaded and embedded at the top of the issue or comment, together with the session metadata. ## Disconnect To disconnect GitHub, go to the [GitHub integration page](https://testingbot.com/members/integrations/github) and click **Disconnect**. Type `Disconnect` in the confirmation dialog to confirm. ![Disconnect GitHub from TestingBot](https://testingbot.com/assets/support/integrations/github/github6-16acde16f9da99b035be428bd917adcfbe7a9159065a9987e1dce15a28ec6a7d.png) Issues that were already linked to your tests stay linked and are not removed. You can reconnect at any time; reconnecting with the same or another GitHub account does not affect previously created issues. ### Looking for more help? Have questions or need more information? Reach out via email or Slack. [Email us](https://testingbot.com/contact/new)[Slack Join our Slack](https://join.slack.com/t/testingb0t/shared_invite/zt-3bcw9xch-jk19~6XPs_xBrsAgAedkCw)