---
title: Issues
description: Automate issue tracking, branch management, project linking, and assignees with Copilot.
---

# Issues

Copilot automates **issue tracking** so that labels, branch creation, project linking, and assignees stay in sync with your Git-Flow workflow. When you open or update an issue (or add labels), the action can create branches, link the issue to boards, assign members, and later notify you of commits and close the issue when branches are merged.

<CardGroup cols={2}>
  <Card title="Labels and branch types" icon="tag" href="/issues/labels-and-branch-types">
    Which labels create which branches (feature, bugfix, docs, chore, hotfix, release) and deploy flow.
  </Card>
  <Card title="Workflow setup" icon="play" href="/issues/workflow-setup">
    Enable the action for issues: events, minimal workflow, and what runs when.
  </Card>
  <Card title="Assignees and projects" icon="people" href="/issues/assignees-and-projects">
    Member assignment and linking issues to GitHub Project boards.
  </Card>
  <Card title="Branch management" icon="git-branch" href="/issues/branch-management">
    Launcher label, naming conventions, and hotfix/release rules.
  </Card>
  <Card title="Notifications and auto-close" icon="bell" href="/issues/notifications-and-auto-close">
    Commit notifications on the issue, reopen on push, and auto-close when merged.
  </Card>
  <Card title="Configuration" icon="gear" href="/issues/configuration">
    All issue-related inputs: labels, branches, size, images, workflow.
  </Card>
  <Card title="Examples" icon="file-code" href="/issues/examples">
    Full workflow YAML and label examples.
  </Card>
</CardGroup>

## Quick summary

| What you do | What Copilot can do |
|-------------|---------------------|
| Open an issue with a **type label** (e.g. `feature`, `bugfix`) | Link to projects, assign members; when **branch launcher** label is added (e.g. `branched`), create the branch from develop (or main for hotfix). |
| Add **`deploy`** to a release/hotfix issue | Trigger the release or hotfix workflow (e.g. deploy). |
| Push commits to the issue’s branch | Post commit notifications on the issue; optionally reopen the issue if it was closed. |
| Merge the branch (e.g. into develop) | Automatically close the issue when the branch is merged. |

**Bugbot** (potential problems) runs on **push** (or single action) and posts findings on the issue and on open PRs; you can ask the bot to fix findings from a comment. See [Bugbot](/bugbot) for full details.

For **step-by-step flows** per issue type (branch naming, source branch, deploy), see the issue type pages: [Feature](/issues/type/feature), [Bugfix](/issues/type/bugfix), [Docs](/issues/type/docs), [Chore](/issues/type/chore), [Hotfix](/issues/type/hotfix), [Release](/issues/type/release).