Github x Copilot

With GitHub Copilot, these tickets (GitHub issues) can be picked up, processed and turned into pull requests with minimal manual work. From a Figma change to a production ready PR, the loop can often be completed in just a few minutes.

This workflow removes friction

PMs no longer need to draft GitHub issues by hand

• Developers spend less time on repetitive implementation tasks

• Copilot, powered by Lyse’s structured context, implements the change and opens a pull request ready for review

Prerequisites

Before using this workflow, make sure you have:

• A GitHub repository connected to Lyse

• A Personal Access Token (PAT) with repository permissions

• GitHub Copilot enabled on your account or organization

• A Figma file where components and naming are aligned with your codebase

Setup guidance

• Connect your GitHub repository to Lyse in the web app, App Integration, GitHub

• Confirm that your PAT has the correct repository and issue permissions

• Enable GitHub Copilot in your account or organization settings

• Follow GitHub’s guide on assigning and completing issues with Copilot:
  Assigning and completing issues with coding agent in GitHub Copilot

• In GitHub, assign Lyse generated tickets to Copilot so it can process them into pull requests automatically

Once everything is in place, the workflow is simple: designers update components in the Figma Design System and publish the library, Lyse detects the changes and creates a ticket in the configured GitHub repository, and Copilot applies the change and opens a pull request. Developers only step in at the review and merge stage.

Benefits

• Time savings : From design change to pull request in minutes instead of hours of coordination.

• Reliability : Copilot works from Lyse’s structured context, which reduces ambiguity and errors.

• Efficiency : Developers focus on review and higher value work while Copilot handles routine updates.