Skip to main content

GitHub Issues

Use the GitHub integration when you want defects in TestFish to link with GitHub Issues or when you need to trigger GitHub Actions workflows from QA events.

Organisation-level setup​

  1. Navigate to Configuration → Integrations → GitHub.
  2. Install the TestFish GitHub App or provide a personal access token with repo scope.
  3. Select the repositories the app can access; TestFish stores installation details securely.

Project-level configuration​

Inside your project open Integrations → GitHub and configure a project integration category:

  • Repository – Choose from authorised repositories. TestFish lists installations so you cannot accidentally pick an unsupported repo.
  • Issue defaults – Map labels, assignees, and default issue title prefixes.
  • Workflow sync – Optionally trigger GitHub Actions workflows when a defect changes state (select workflow, ref, and inputs).
  • Status mapping – Align TestFish workflow states with GitHub labels or project boards.

Working with defects​

  • Creating a defect in TestFish can create a linked GitHub issue with title, body, attachments, labels, and assignees.
  • Updates to the defect (status, assignee, description) can push comments or field updates back to GitHub depending on your configuration.
  • The GitHub issue link is always displayed on the card so teams can jump directly into GitHub.
  • Use the Search issues action to link existing GitHub issues without duplicating them.

Tips​

  • Use a dedicated integration API token for automation and webhooks; generate one via project API tokens (integration type).
  • Leverage GitHub labels to reflect TestFish severities or milestone names for quick filtering on the GitHub side.
  • Combine with the automated test run webhook to trigger reruns or deployments in GitHub Actions.