Datasource Management

Introduction

Entelligence offers powerful integration capabilities that allow you to connect and synchronize multiple data sources, enabling seamless management of code repositories, issues, and pull requests across various platforms. This guide explains how the data source management system works and walks you through the setup process.

Key Features

• Multi-platform integration (GitHub, Jira, Linear, etc.)

• Real-time synchronization through webhooks

• Automated PR review bot

• Intelligent issue solution suggestions

• Continuous updates and monitoring

• Centralized data source management

How Data Source Management Works

Entelligence uses a centralized data source management system that:

1. Maintains connections to your various development tools and platforms

2. Tracks the synchronization status of each data source

3. Provides automated update mechanisms through webhooks

4. Ensures data consistency across all integrated platforms

Code Bases and Last Updated Time

Step 1:

All datasource management can be found as a part of the user profile.

Step 2:

Within the user profile, admins will have access to update the data sources tab. Each data source will list the last updated time as well as other relevant information such as the latest commit hash, PR number or issue number. You can setup continuous updates through a webhook for each of your codebases by clicking on the Continuous Updates button. This will configure the webhook to listen to all PR merge events in your Github repo and update Entelligence. This feature allows for continuous refreshing to keep all code bases, issues, and PRs current. Alternatively, you can click the refresh button to auto trigger a refresh for any datasource.

Pull Request Review Bot and Issue Solutions

Step 3:

For each code base, enable the pull request review bot and issue solutions. These tools will directly respond to every issue in GitHub, Jira, or other product management tools. Please refer to the PR review bot section for detailed explanations for the review bot capabilities and configuration.

Step 4:

Set up continuous updates. This will establish a webhook to listen to real-time pushes made to the code base. The last updated time and commit id will be listed every time the refresh has been triggered. This will set up a webhook in your codebase which requires that we have webhook write permissions for the codebase.

Step 5:

Apply the same steps for all issues and pull requests, regardless of whether they are in GitHub, Linear, Jira, etc.

Step 6:

Confirm the refresh status. For instance, the Princeton-nlp/SWE-agent is now entirely up to date.