GitHub Copilot Extension

Flightcrew has a GitHub Copilot extension that you can use to streamline your workflow right from your IDE. You can retrieve recommendations, ask for clarifications, and apply them directly from the extension, making it easier to optimize your codebase.

See Flightcrew for Copilot in the GitHub Marketplace.

Here's a demo highlighting these key features:

Prerequisites

• You must be an organization owner or have admin permissions in a repository.
• You must have access to GitHub Copilot.

Installation

Permissions

You will need to authorize the extension in order to use it (@flightcrewhq-copilot [message]).

The extension will ask for the following permissions:

• metadata: read - list repositories and get basic information
• contents: read - read the repository file that you attach to your chat messages
• copilot chat: access - read the chat messages you send to the extension
• copilot editor context: read - read the file(s) your are currently editing in your IDE

App Installation

1. Navigate to Settings in Flightcrew and select Authorize GitHub Copilot Extension, or find our extension in the GitHub Marketplace.

2. You will be redirected to GitHub. You'll see the list of permissions that the extension is requesting. Click on 'Authorize flightcrewhq-copilot' to authorize the extension.

   

3. Navigate to Settings in Flightcrew and select Install GitHub Copilot Extension.

4. You will be redirected to GitHub. Select the organization where you want to install the extension.

5. Specify whether you wish to install the extension in all repositories of the selected GitHub organization or in specific repositories.

   

6. Follow the prompts to install the extension and complete the installation.

App Usage Requirements

Supported Languages

Flightcrew supports the following config formats:

Format	Support
Raw YAML	Supported
AWS CDK	Supported
CDK8s	Supported
CloudFormation	Supported
Dagger	Supported
Helm	Supported
OpenTofu	Supported
Pulumi	Supported
Terraform	Supported
YTT	Supported

Workload Mapping

Flightcrew automatically links your repository's config files to the corresponding resources running live in your cloud. This process helps ensure that generating pull requests from Flightcrew edits the proper config files.

• Successful mapping: If Flightcrew successfully links the resource to its config files, you'll see "Connected to" displayed above the recommended code change, indicating that the link between your repository code and cloud resource is established.

  

• Unsuccessful mapping: If Flightcrew is unable to links the resource, it will display "No source file connected." under the resource name. Clicking the "Connect to a source file" link will open a modal where you can manually navigate to and select the appropriate configuration file in your repository.

  

Flightcrew will attempt to keep these up-to-date even as files change or move around, but you can always update or change the connected files via this interface as needed. A user-entered mapping will override anything else.

Interacting with the Extension

Prompts

Just ask @flightcrewhq-copilot What can you do? to get started.

Here are a few example prompts you can use:

• @flightcrewhq-copilot What are my highest priority action items?
• @flightcrewhq-copilot Give me a recommendation for this file.
• @flightcrewhq-copilot Give me a resiliency fix for this file.
• @flightcrewhq-copilot Explain to me how this recommendation / resiliency helps.
• @flightcrewhq-copilot What workloads is this file connected to?

Apply Changes in Editor

When the Flightcrew Copilot extension sends back a code snippet, you can hover over it to see the "Apply in Editor" button. Copilot will attempt to apply the changes in your file. You can review the changes before saving or discarding them.

Alternatively, you can copy the code snippet and manually edit your file.

FAQ

Help! I'm having trouble with the chat context.

GitHub Copilot Chat is in public beta. If you are getting stuck with the same responses, then you may need to restart your IDE.

If the problems persist, please reach out for support.

How does the GitHub app handle tokens?

When you authorize the Flightcrew Copilot extension, Flightcrew stores your GitHub username to associate your GitHub account with a Flightcrew account.

When you send messages to the extension, the chat context will contain your GitHub token, which Flightcrew can use find the Flightcrew data to send back to you.

No tokens or secrets are stored by Flightcrew.

Can Flightcrew modify my files?

Flightcrew does not have the ability to directly modify your files from the Copilot chat.

However, you may click "Apply in Editor" to apply a Flightcrew recommendation directly in your IDE. The user has full control over any changes and can review them before saving.

How do I update what repositories the app has access to?

Go to Settings > Applications > Installed GitHub Apps and select flightcrewhq. Click on the "Configure" button. On this page, you can change what repositories the app has access to.

If the app isn't showing up, double check you're looking at the right settings scope - it may be in a different organization.

How do I uninstall the app?

To uninstall the app, go to Settings > Applications > Installed GitHub Apps and select flightcrewhq. Click on the "Configure" button. At the bottom of the page, you can hit "Uninstall".

To remove authorization to the app, go to Settings > Applications > Authorized GitHub Apps and revoke access.

If the app isn't showing up, double check you're looking at the right settings scope - it may be in a different organization.