Skip to content

Conversation

@BrunoV21
Copy link
Owner

@BrunoV21 BrunoV21 commented Nov 1, 2025

This pull request introduces comprehensive pull request management capabilities, including branch operations, PR creation, and AI-powered description generation. The changes enhance both the backend API and frontend UI, with support for GitHub and future extensibility to other Git providers.

Features

  • Added pull request management methods to Git provider fetchers, including branch listing, validation, and PR creation
  • Implemented API endpoints for GitHub branch operations and pull request creation with AI-generated descriptions
  • Added branch comparison method to fetch diff commits between branches
  • Introduced WebSocket endpoint for AI-powered pull request description generation
  • Implemented pull request generation feature with branch selection and automated PR creation
  • Added dropdown menu for release notes and PR creation with improved navigation flow
  • Consolidated PR mode sections into a unified output layout
  • Merged PR generation and creation into a single action button
  • Added progress indicators for diff fetching and description generation
  • Implemented branch sorting in branch listing and validation responses

Bug Fixes

  • Disabled release mode button when multiple repos are selected or non-GitHub host is used
  • Added tooltips to disabled menu buttons explaining repository selection and GitHub requirements
  • Fixed auto-scroll functionality for PR description updates and summary section

Improvements

  • Added slide animation and styling for options menu with improved button layout and accessibility
  • Standardized button sizing and layout for recap controls
  • Removed unused CSS class definition
  • Replaced PR validation message with popup notifications for creation success and errors
  • Adjusted PR mode layout to horizontal inline design with improved spacing
  • Updated PR branch selector layout spacing and alignment
  • Updated PR generate button styling for consistent sizing and disabled state appearance

Refactoring

  • Consolidated PR mode sections into unified output layout
  • Merged PR generation and creation into single action button

Documentation

  • No documentation changes in this pull request

Notes:
Please ensure all tests pass before merging. Special attention should be given to the new PR management features and UI changes.

BrunoV21 and others added 24 commits October 7, 2025 12:34
This change introduces three new abstract methods to the base fetcher class for managing branches and pull requests: `get_branches()`, `get_valid_target_branches()`, and `create_pull_request()`. The GitHub fetcher now includes full implementations with proper error handling, API integration, and support for reviewers, assignees, and labels. Azure DevOps, GitLab, and URL fetchers include stub implementations that raise NotImplementedError with clear messages indicating future support. Comprehensive unit tests validate the GitHub implementation's behavior for successful operations, error scenarios, and API failures.
… branch validation, and pull request creation with LLM-generated descriptions, including supporting schema models and service utilities.
… WebSocket endpoint with dedicated system prompt
…ed PR creation

Implemented a new PR mode that allows users to select source and target branches, view commit diffs, generate AI-powered pull request descriptions via WebSocket streaming, and automatically create pull requests on GitHub. The feature includes comprehensive validation, loading states, error handling, and a responsive UI that integrates seamlessly with the existing recap and release modes.
This commit adjusts button dimensions and padding across recap action buttons and menu options for consistent visual hierarchy and fixed sizing
This commit merges the separate PR diff and description sections into the existing actions log and summary log areas, conditionally rendering content based on mode
This commit introduces automatic sorting of branches in BranchListResponse and ValidTargetBranchesResponse schemas, prioritizing main/master branches at the top followed by alphabetically sorted remaining branches
@BrunoV21 BrunoV21 closed this Nov 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants