✨ Add Sentry Integration to PR Pilot

[pr-pilot-ai[bot]]

Description

This PR introduces a new Sentry integration to PR Pilot. Users can now enter their Sentry API key in the dashboard, allowing PR Pilot to interact with the Sentry API to search for issues and events.

Changes Made

• Model: Added SentryIntegration model to accounts/models.py to store the Sentry API key.
• Template: Updated dashboard/templates/integrations/sentry.html with a form to enter the Sentry API key.
• View: Updated IntegrationView class in dashboard/views/integrations.py to handle the Sentry API key form submission.
• Agent Tools: Implemented Sentry agent tools in engine/agents/integration_tools/sentry_tools.py.
• Tests: Wrote unit tests for the new tools in engine/agents/tests/test_sentry_tools.py.
• Tool Registration: Updated tool registration mechanism in engine/agents/integration_tools/__init__.py to include the new Sentry tools.

Related Issue

• Issue #189: Add missing migration for the SentryIntegration model.

How to Test

1. Go to the integrations page in the dashboard.
2. Enter a valid Sentry API key in the provided form.
3. Verify that the key is saved and that the Sentry tools can fetch issues and events using the API key.

Notes

This integration enhances PR Pilot's capabilities by allowing it to interact with Sentry, providing users with more comprehensive tools for issue and event management.

[pr-pilot-ai[bot]]

The following tests failed due to the changes introduced in this PR:

1. api/tests/test_api.py

   • test_create_task_via_api
   • test_create_task_via_api_with_pr_number
   • test_create_task_via_api__repo_not_found
   • test_image_upload
   • test_create_task_via_api__branch_setting
   • test_list_tasks

2. engine/agents/tests/test_tools.py

   • test_list_directories

3. engine/tests/test_models.py

   • test_credits
   • test_task_only_schedules_if_user_can_write
   • test_task_would_reach_rate_limit

4. engine/tests/test_task_engine.py

   • test_bill_creation_correctness
   • test_task_status_set_correctly
   • test_pr_number_set
   • test_handles_custom_branch_correctly
   • test_create_unique_branch_name__existing_branch
   • test_create_unique_branch_name__slug

5. engine/tests/test_task_scheduler.py

   • test_user_can_write

6. webhooks/test_webhooks.py

   • test_install_repository_truncates_api_key_name

Cause of Failures

The errors are primarily due to the missing database table accounts_sentryintegration. This table is required by the new SentryIntegration model introduced in the PR. The tests fail because the table does not exist in the test database.

Suggested Fix

1. Add Missing Migration: Ensure that the migration for the SentryIntegration model is created and applied. This can be done by running:

   python manage.py makemigrations accounts
   python manage.py migrate

2. Update Tests: Ensure that the test setup includes the new migration. This can be done by adding the migration step in the test setup.

Example Code Snippet for Migration

# In your test setup file or conftest.py
import pytest
from django.core.management import call_command

@pytest.fixture(scope='session')
def django_db_setup():
    call_command('migrate', run_syncdb=True)

By ensuring the migration is applied, the tests should be able to find the accounts_sentryintegration table and pass successfully.