Skip to main content

​
Overview

The Copilot Connections page allows administrators to configure GitHub Copilot API connections within G360. Once configured, the connection can be used to authenticate and access GitHub Copilot APIs using a valid GitHub token. Using this feature, users can:
  • Create Copilot connections
  • Manage GitHub authentication tokens
  • Test connection validity
  • Store and manage multiple API connections
  • Monitor connection usage

​
Prerequisites

Before configuring a Copilot connection, ensure you have:
  • Access to the G360 platform
  • Appropriate permissions to manage integrations
  • A valid GitHub token
  • Access to the GitHub Copilot services that will be used
  1. Open G360.
  2. Navigate to Integration.
  3. Select Copilot Connections.
The Copilot Connections page displays all configured Copilot API connections.

​
Understanding the Copilot Connections Page

The page contains the following information:
  • API Key Name
  • Provider
  • Status
  • Created At
  • Last Used
  • Available Actions
If no connections exist, the table will remain empty until a connection is created.

​
Create a New Copilot Connection

  1. Click Add Connection.
  2. The Add Copilot Connection window will appear.

​
Configure Connection Details

​
Connection Name

Enter a unique name for the connection. Examples:
  • GitHub Copilot Production
  • Engineering Copilot
  • Internal Copilot Access
  • Development Copilot
Use descriptive names to make connections easier to identify and manage.

​
GitHub Token

Enter a valid GitHub token. The token is used to authenticate requests to GitHub Copilot services.
The token must remain active and have sufficient permissions for the services being accessed.

​
Test the Connection

Before saving the configuration:
  1. Click Test Connection.
  2. Wait for the validation process to complete.

​
Expected Result

  • If the token is valid, the connection test will succeed.
  • If validation fails, verify the GitHub token and retry the test.

​
Save the Connection

  1. After successful validation, click Save Connection.
  2. The connection will be added to the Copilot Connections list.

​
Managing Existing Connections

Administrators can view all configured connections from the Copilot Connections page. The table provides visibility into:
  • Connection name
  • Provider information
  • Current status
  • Creation date
  • Last usage date
This information helps administrators monitor active Copilot integrations.

​
Monitoring Connection Usage

The Last Used column provides visibility into when a connection was last utilized. This information can help identify:
  • Active connections
  • Unused connections
  • Connections requiring review or cleanup

​
Troubleshooting

​
Connection Test Failed

Possible causes:
  • Invalid GitHub token
  • Expired GitHub token
  • Network connectivity issues
  • Authentication failures
Recommended actions:
  • Verify the GitHub token
  • Generate a new token if necessary
  • Retry the connection test
  • Confirm network connectivity

​
Connection Not Appearing

Possible causes:
  • Connection was not saved successfully
  • Validation failed before saving
Recommended actions:
  • Repeat the connection creation process
  • Verify all required fields are completed
  • Save the connection after a successful test

​
Best Practices

  • Use descriptive connection names
  • Regularly review active connections
  • Remove unused connections
  • Rotate GitHub tokens according to organizational security policies
  • Test connections after updating credentials

​
Summary

Copilot Connections allow administrators to securely configure GitHub Copilot authentication within G360. By creating and managing connection profiles, organizations can simplify API access management while maintaining visibility into connection usage and status.