Skip to content

fix(fuse) support FUSE submounts and fix virtiofs mount semantics #1195

fix(fuse) support FUSE submounts and fix virtiofs mount semantics

fix(fuse) support FUSE submounts and fix virtiofs mount semantics #1195

Workflow file for this run

name: Claude Code Review
on:
pull_request_target:
types: [opened, synchronize]
jobs:
claude-review:
runs-on: ubuntu-latest
permissions:
contents: write
pull-requests: write
issues: write
id-token: write
actions: read
steps:
- name: Generate GitHub App token
id: app-token
uses: actions/create-github-app-token@v2
with:
app-id: ${{ secrets.APP_ID }}
private-key: ${{ secrets.APP_PRIVATE_KEY }}
- name: Checkout repository
uses: actions/checkout@v5
with:
repository: ${{ github.event.pull_request.head.repo.full_name }}
ref: ${{ github.event.pull_request.head.ref }}
fetch-depth: 20
- name: Run Claude Code Review
uses: anthropics/claude-code-action@v1
env:
ANTHROPIC_BASE_URL: https://api.deepseek.com/anthropic
API_TIMEOUT_MS: 600000
ANTHROPIC_MODEL: deepseek-reasoner
ANTHROPIC_SMALL_FAST_MODEL: deepseek-chat
with:
# Enable progress tracking
track_progress: true
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
github_token: ${{ steps.app-token.outputs.token }}
allowed_non_write_users: "*"
claude_args: |
--max-turns 200 --allowedTools "mcp__github_inline_comment__create_inline_comment,Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*)"
prompt: |
REPO: ${{ github.event.pull_request.head.repo.full_name }}
PR NUMBER: ${{ github.event.pull_request.number }}
# project background
DragonOS is a 64-bit operating system with a completely independent kernel,
designed for lightweight cloud computing scenarios, offering Linux binary compatibility.
It aims to provide lightweight, high-performance solutions for containerized workloads.
Perform a comprehensive code review with the following focus areas:
1. **Code Quality**
- Clean code principles and best practices
- Proper error handling and edge cases
- Code readability and maintainability
2. **Security**
- Check for potential security vulnerabilities
- Validate input sanitization
- Review authentication/authorization logic
3. **Performance**
- Identify potential performance bottlenecks
- Review database queries for efficiency
- Check for memory leaks or resource issues
4. **Testing**
- Verify adequate test coverage
- Review test quality and edge cases
- Check for missing test scenarios
5. **Documentation**
- Ensure code is properly documented
- Verify README updates for new features
- Check API documentation accuracy
Provide detailed feedback using inline comments for specific issues.
Use top-level comments for general observations or praise.