Update compatibility with Blacklake

[terales]

Update compatibility with Blacklake

[coderabbitai]

Warning

Review limit reached

@terales, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 26 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8f0aaec0-6633-4149-9ed1-52c5d97773a7

📥 Commits

Reviewing files that changed from the base of the PR and between ca4e43a and 46d02de.

📒 Files selected for processing (1)

• Apps.GitLab/Apps.GitLab.csproj

Walkthrough

GitLab file requests now support an optional content name, which is propagated to downloaded-file processing and used instead of the derived filename when provided. The project version is incremented from 1.0.16 to 1.0.17.

Changes

Content Name Propagation

Layer / File(s)	Summary
Content name request and processing Apps.GitLab/Models/Respository/Requests/GetFileRequest.cs, Apps.GitLab/Utils/File/FileHelper.cs	Adds nullable ContentName request data and applies it to processed file metadata, with filename fallback.
Repository action integration Apps.GitLab/Actions/RepositoryActions.cs, Apps.GitLab/Apps.GitLab.csproj	Reformats the file-processing call without changing its arguments and increments the project version to 1.0.17.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: mathijs-bb

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the main goal of the change: improving Blacklake compatibility.
Description check	✅ Passed	The description is related to the changeset and states the same Blacklake compatibility goal.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch develop

---

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

_{Comment @coderabbitai help to get the list of available commands.}