gitlab mr 状态可配置
满足不同gitlab版本state,merge_status
Summary by CodeRabbit
-
New Features
- Added support for configurable GitLab merge request status handling, allowing for more flexible recognition of merge request states.
-
Documentation
- Updated configuration documentation to describe the new GitLab merge request status parameter and provide additional reference information.
Walkthrough
A new configuration constant, GITLAB_MERGE_REQUEST_STATUS, was introduced to centralize GitLab merge request state/merge status combinations. The function is_merge_request_opened was refactored to use this new configuration for status checks, and related documentation was updated to describe the new parameter.
Changes
| File(s) | Change Summary |
|---|---|
| config/config.py | Added GITLAB_MERGE_REQUEST_STATUS constant for GitLab merge request state/status combinations. |
| doc/config.md | Documented the new GITLAB_MERGE_REQUEST_STATUS config parameter and made a minor formatting fix. |
| gitlab_integration/gitlab_fetcher.py | Refactored is_merge_request_opened to use the new config constant; added relevant import. |
Sequence Diagram(s)
sequenceDiagram
participant GitLab
participant Fetcher as gitlab_fetcher.py
participant Config as config.py
GitLab->>Fetcher: Send merge request payload
Fetcher->>Config: Access GITLAB_MERGE_REQUEST_STATUS
Fetcher->>Fetcher: Check payload's state/merge_status against config list
alt Match found
Fetcher->>GitLab: Return True (opened)
else No match
Fetcher->>GitLab: Return False (not opened)
end
Possibly related PRs
- mimo-x/Code-Review-GPT-Gitlab#31: Refactored the same
is_merge_request_openedfunction, now further improved to use a configuration-driven approach for merge request status checks.
Poem
In the warren of code, a change takes root,
Configs now guide what statuses suit.
No more hardcoded, the logic is neat—
Merge requests checked by a list complete.
With docs refreshed and functions refined,
This rabbit hops forward, with clarity in mind! 🐇✨
✨ Finishing Touches
- [ ] 📝 Generate Docstrings
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
🪧 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. -
Explain this complex logic. -
Open a follow-up GitHub issue for this discussion.
-
- Files and specific lines of code (under the "Files changed" tab): Tag
@coderabbitaiin a new review comment at the desired location with your query. Examples:-
@coderabbitai explain this code block. -
@coderabbitai modularize this function.
-
- PR comments: Tag
@coderabbitaiin 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 explain its main purpose. -
@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.
-
Support
Need help? Create a ticket on our support page for assistance with any issues or questions.
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 pauseto pause the reviews on a PR. -
@coderabbitai resumeto resume the paused reviews. -
@coderabbitai reviewto trigger an incremental review. This is useful when automatic reviews are disabled for the repository. -
@coderabbitai full reviewto do a full review from scratch and review all the files again. -
@coderabbitai summaryto regenerate the summary of the PR. -
@coderabbitai generate docstringsto generate docstrings for this PR. -
@coderabbitai generate sequence diagramto generate a sequence diagram of the changes in this PR. -
@coderabbitai resolveresolve all the CodeRabbit review comments. -
@coderabbitai configurationto show the current CodeRabbit configuration for the repository. -
@coderabbitai helpto get help.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
CodeRabbit Configuration File (.coderabbit.yaml)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yamlfile 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.