修复 Gitlab 不同版本 mr 请求区别

[mimo-x]

Fix some issues -- #26 #30 #28

thanks ~

This issue persists across multiple versions of GitLab ~~ 🤔

Summary by CodeRabbit

• New Features

  • Enhanced merge request processing in the GitLab integration by introducing a dedicated mechanism to assess merge request statuses. This update ensures that both active and mergeable requests are accurately identified.

• Bug Fixes

  • Improved error logging in the merge request handling process by including additional context for better debugging.

• Refactor

  • Simplified the logic within the webhook handler for merge request events, leading to more robust error handling and improved overall system reliability.

[coderabbitai]

Walkthrough

The changes introduce a new function, is_merge_request_opened, in the GitLab integration module. This function encapsulates the logic for verifying if a merge request is considered open by evaluating combinations of state and merge status with error handling. Additionally, the webhook listener has been updated to replace its inline conditional check with a call to this new function, thereby simplifying the control flow. The error logging in the review engine has also been enhanced to provide more context during failures.

Changes

File	Change Summary
gitlab_integration/gitlab_fetcher.py	Added the is_merge_request_opened function to determine merge request openness with error handling; minor formatting change (newline added) in _build_authenticated_url.
gitlab_integration/webhook_listener.py	Replaced the inline conditional check for merge request state with a call to is_merge_request_opened and added the corresponding import.
review_engine/handler/default_handler.py	Updated the error logging in default_handle method to include merge_info for enhanced context during failures.

Sequence Diagram(s)

sequenceDiagram
    participant WL as WebhookListener
    participant GF as GitLabFetcher

    WL->>GF: Call is_merge_request_opened(gitlab_payload)
    GF-->>WL: Return Boolean result (True/False)
    WL->>WL: Proceed with merge request handling

Loading

Poem

I'm a hopping rabbit, sleek and bright,
New code springs to life in the pale moonlight.
With merge requests checked in a single call,
I dance and thump throughout the hall.
Code carrots crunch as we celebrate it all!
🐰💕

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1271148 and 77d5be0.

📒 Files selected for processing (2)

• gitlab_integration/gitlab_fetcher.py (2 hunks)
• review_engine/handler/default_handler.py (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• gitlab_integration/gitlab_fetcher.py

🔇 Additional comments (1)

review_engine/handler/default_handler.py (1)

127-129: Good enhancement to error logging!

Adding merge_info to the error log provides valuable context for debugging issues with GitLab merge requests. This improvement helps diagnose problems that might occur across different GitLab versions, directly supporting the PR objectives of fixing issues #26, #30, and #28.

✨ Finishing Touches

• 📝 Docstrings were successfully generated. (🔄 Check again to generate again)

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Note

Generated docstrings for this pull request at #32