[shenxianpeng]

git-bot-feedback 0.12.1 gives cpp-linter clients for Gitea, Forgejo and GitLab, but the docs only talk about GitHub. This adds one page, "Supported Git Servers" (after "Permissions" in the nav), with:

• how the server is detected and which token variable is read,
• a table of which feedback features work on which server,
• per server: the differences to GitHub and a minimal CI example.

Docs only, plus forgejo in the cspell words. mkdocs build --strict and pre-commit pass.

What I tested

I ran cpp-linter against real servers before writing the page. The CI environment variables were set by hand on a normal machine (no Gitea runner or GitLab Runner was involved), with the pull request payload taken from the server's own API.

Gitea 28.3.0 (local instance, main at d26b5fe, clang 18, token of a collaborator with write access):

Run	Result
PR with problems	changed files found, thread comment, review that requests changes with 3 suggestions, outputs, step summary file, 5 annotations in the log
same run again	review comments reused, no second review, still one thread comment
PR fixed, default --no-lgtm	thread comment removed. Dismissing the old review fails with 403 Must be repo admin (logged as an error, exit code 0), so the review that requested changes stays
PR fixed, --no-lgtm=false	approving review posted, Gitea marks the old review as dismissed
push event	last commit analyzed, "thread comments is limited to pull requests only" in the log
no GITEA_TOKEN	analysis runs, then posting fails with exit code 1

GitLab 19.6.0-pre (gitlab.com, private project, release binary 2.0.0-rc.25, clang 18, personal access token):

Run	Result
merge request with problems	3 diff threads with suggestions, review summary, changes requested, report comment, no draft notes left over
same run again	threads reused, no duplicates
merge request fixed, --no-lgtm=false	the 3 threads resolved, merge request approved, report comment replaced by the LGTM one
push pipeline	no comments, "thread comments is limited to merge requests only" in the log
no GITLAB_TOKEN	fails with exit code 1 while getting the changed files

Not tested: Forgejo on a real server (that section follows git-bot-feedback's README, I only checked that FORGEJO_ACTIONS and FORGEJO_TOKEN select the client and authenticate), and the two CI examples under a real runner. The GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }} line in particular is from Gitea's docs, not from a run. Tell me if you would rather leave the examples out.

Things I noticed on the way

Not part of this PR. I list them so they are not lost, and can file or fix whichever you want:

1. GitLab, private project, no token: the error says "Failed to get merge request raw diffs (requires GitLab v17.9 or newer)", but the real cause is a 404 because of the missing token. The "No GITLAB_TOKEN" warning is printed twice.
2. Gitea with a non-admin token: the failed dismissal (see the table) leaves a stale blocking review with the default options. The page recommends --no-lgtm=false or --passive-reviews for now.
3. A review suggestion that only holds a clang-format change gets the heading "clang-tidy suggestion".
4. On GitLab, --step-summary does nothing without saying so, and --file-annotations prints each annotation as a debug struct. The page says to turn annotations off there.
5. The help text of --thread-comments and --files-changed-only only mentions GITHUB_TOKEN.

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 37 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Repository UI (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: 3fb85936-816a-42dd-a036-7675f4812436

Commits

Reviewing files that changed from the base of the PR and between d26b5fe and b675eed.

Files selected for processing: 3

• cspell.config.yml
• docs/docs/git-servers.md
• docs/mkdocs.yml

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

Share

• X
• Mastodon
• Reddit
• LinkedIn