feat: Add Gitea pull request and comment endpoints#68
Merged
Meldiron merged 9 commits intoutopia-php:mainfrom Mar 18, 2026
Merged
feat: Add Gitea pull request and comment endpoints#68Meldiron merged 9 commits intoutopia-php:mainfrom
Meldiron merged 9 commits intoutopia-php:mainfrom
Conversation
- Implement getPullRequest to fetch PR details - Implement getPullRequestFromBranch to find PR by branch name - Implement createPullRequest to create new PRs - Implement createComment, getComment, updateComment for PR comments - Add comprehensive tests with full workflow coverage - Add edge case tests for invalid inputs - Follow PR utopia-php#64 null safety pattern Tests: 7 new tests, all passing
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughThe Gitea VCS adapter was extended: Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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. Comment Tip CodeRabbit can use OpenGrep to find security vulnerabilities and bugs across 17+ programming languages.OpenGrep is compatible with Semgrep configurations. Add an |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3277ea7614
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
tests/VCS/Adapter/GiteaTest.php (1)
106-116: These PR tests never add a commit to the head branch.Lines 106-108 and the same pattern in the other PR tests create a feature branch, but the subsequent
createFile()calls still write to the default branch.src/VCS/Adapter/Git/Gitea.php'screateFile()payload has no branch/ref field, so these cases are not actually exercising a branch with head-only changes and can get flaky if Gitea rejects no-op PRs.I’d either extend
createFile()to accept a branch/ref for tests, or create the feature-branch commit through the contents API directly before opening the PR.Also applies to: 152-163, 448-463, 665-676
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/VCS/Adapter/GiteaTest.php` around lines 106 - 116, The tests create a branch with createBranch() but then call createFile() which currently writes to the default branch (Gitea::createFile lacks a branch/ref), so the PR head has no commits; update the tests by either (A) extending createFile() to accept an optional branch/ref parameter and using that when creating test files on 'comment-test' (and adjust the Gitea adapter implementation to include the ref in the payload), or (B) create the branch commit directly via the Gitea contents API before calling createPullRequest(); apply the chosen approach consistently for the other failing tests that use createBranch() + createFile() (the blocks around lines referenced).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/VCS/Adapter/Git/Gitea.php`:
- Around line 449-464: The current call builds $url with
"?state=open&sort=recentupdate&limit=1" and then filters $responseBody for the
branch, which can miss PRs; remove the "limit=1" (or replace with a server-side
head filter if Gitea supports it) so the API returns all matching open PRs, then
keep the existing loop over $responseBody ($response, $responseBody, $prHead,
$prHeadRef) to find the PR whose head ref equals $branch and return it; ensure
you still handle an empty result by returning [].
---
Nitpick comments:
In `@tests/VCS/Adapter/GiteaTest.php`:
- Around line 106-116: The tests create a branch with createBranch() but then
call createFile() which currently writes to the default branch
(Gitea::createFile lacks a branch/ref), so the PR head has no commits; update
the tests by either (A) extending createFile() to accept an optional branch/ref
parameter and using that when creating test files on 'comment-test' (and adjust
the Gitea adapter implementation to include the ref in the payload), or (B)
create the branch commit directly via the Gitea contents API before calling
createPullRequest(); apply the chosen approach consistently for the other
failing tests that use createBranch() + createFile() (the blocks around lines
referenced).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: ff55d472-6fd1-4ebf-86db-9d78ff264369
📒 Files selected for processing (2)
src/VCS/Adapter/Git/Gitea.phptests/VCS/Adapter/GiteaTest.php
- Remove limit=1 from getPullRequestFromBranch to fetch all PRs - Add branch parameter to createFile for branch-specific commits - Update tests to commit files to feature branches
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (2)
tests/VCS/Adapter/GiteaTest.php (2)
101-145: Always delete the test repo infinally.This test creates remote state and only cleans it up on the happy path. Any failed assertion or API error before Line 144 leaks repositories into the shared Gitea instance and can make later runs flaky.
♻️ Suggested cleanup pattern
public function testCommentWorkflow(): void { $repositoryName = 'test-comment-workflow-' . \uniqid(); - $this->vcsAdapter->createRepository(self::$owner, $repositoryName, false); - - $this->vcsAdapter->createFile(self::$owner, $repositoryName, 'README.md', '# Test'); - $this->vcsAdapter->createBranch(self::$owner, $repositoryName, 'comment-test', 'main'); - $this->vcsAdapter->createFile(self::$owner, $repositoryName, 'test.txt', 'test', 'Add test file', 'comment-test'); - - $pr = $this->vcsAdapter->createPullRequest( - self::$owner, - $repositoryName, - 'Comment Test PR', - 'comment-test', - 'main' - ); + $this->vcsAdapter->createRepository(self::$owner, $repositoryName, false); + + try { + $this->vcsAdapter->createFile(self::$owner, $repositoryName, 'README.md', '# Test'); + $this->vcsAdapter->createBranch(self::$owner, $repositoryName, 'comment-test', 'main'); + $this->vcsAdapter->createFile(self::$owner, $repositoryName, 'test.txt', 'test', 'Add test file', 'comment-test'); + + $pr = $this->vcsAdapter->createPullRequest( + self::$owner, + $repositoryName, + 'Comment Test PR', + 'comment-test', + 'main' + ); - $prNumber = $pr['number'] ?? 0; - $this->assertGreaterThan(0, $prNumber); + $prNumber = $pr['number'] ?? 0; + $this->assertGreaterThan(0, $prNumber); - $originalComment = 'This is a test comment'; - $commentId = $this->vcsAdapter->createComment(self::$owner, $repositoryName, $prNumber, $originalComment); + $originalComment = 'This is a test comment'; + $commentId = $this->vcsAdapter->createComment(self::$owner, $repositoryName, $prNumber, $originalComment); - $this->assertNotEmpty($commentId); - $this->assertIsString($commentId); + $this->assertNotEmpty($commentId); + $this->assertIsString($commentId); - $retrievedComment = $this->vcsAdapter->getComment(self::$owner, $repositoryName, $commentId); - $this->assertSame($originalComment, $retrievedComment); + $retrievedComment = $this->vcsAdapter->getComment(self::$owner, $repositoryName, $commentId); + $this->assertSame($originalComment, $retrievedComment); + } finally { + $this->vcsAdapter->deleteRepository(self::$owner, $repositoryName); + } - - $this->vcsAdapter->deleteRepository(self::$owner, $repositoryName); }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/VCS/Adapter/GiteaTest.php` around lines 101 - 145, The testCommentWorkflow method currently only deletes the created repository on the happy path; wrap the main test logic in a try/finally so the cleanup always runs: declare repositoryName as you already do, then enclose creation/assertions (calls to createRepository, createFile, createBranch, createPullRequest, createComment, getComment, updateComment, etc.) in a try block and call $this->vcsAdapter->deleteRepository(self::$owner, $repositoryName) inside a finally block to ensure the repo is removed even on failures.
193-205: Make the invalid-case tests assert one concrete contract.These tests currently pass on any string/array, including raw Gitea error payloads, so they do not lock in the adapter’s not-found behavior. Assert a specific outcome (
''/[]orexpectException()), not just the type.Also applies to: 481-493
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/VCS/Adapter/GiteaTest.php` around lines 193 - 205, The test testGetCommentInvalidId currently only asserts the return is a string allowing raw API errors; update it (and the similar tests around the other block) to assert a single concrete contract for the "not found" case: either assertSame('', $result) if adapter should return an empty string, or change the test to expectException(...) if the adapter should throw; locate and modify the call to getComment in testGetCommentInvalidId (and the analogous tests) and replace the loose assertIsString/assertIsArray with a specific assertion matching the adapter's intended behavior, keeping createRepository/createFile/deleteRepository setup/teardown intact.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/VCS/Adapter/Git/Gitea.php`:
- Around line 191-203: The Gitea adapter added an optional $branch parameter to
Gitea::createFile(string $owner, string $repositoryName, string $filepath,
string $content, string $message = 'Add file', string $branch = '') but the
abstract Git::createFile() contract still defines only five parameters; make the
branch behavior part of the shared contract by updating the abstract method
signature in Git::createFile to accept the optional sixth parameter (string
$branch = '') and then update all concrete implementations and any call sites to
accept/forward this optional $branch argument (or alternatively add a new
branch-aware method on Git if you prefer to keep the old signature, ensuring
Git::createFile remains unchanged and adding e.g. createFileOnBranch with the
same parameters used in Gitea::createFile).
- Around line 456-471: Replace the paginated list fetch with a direct PR lookup
using Gitea's dedicated endpoint: construct the URL
"/repos/{$owner}/{$repositoryName}/pulls/{$targetBranch}/{$branch}" (using the
current target/base branch variable and the source $branch), call
$this->call(self::METHOD_GET, $url, ['Authorization' => "token
$this->accessToken"]), then parse the returned response body and return the PR
if present (or [] on not-found/error). Update the logic that currently iterates
$responseBody/$prHeadRef to instead use this single-call flow so pagination is
avoided.
- Around line 382-391: The createPullRequest() and getPullRequest() methods
currently return $response['body'] without checking HTTP status, so non-2xx
responses (e.g. 422/404/401) propagate error payloads; update both methods to
mirror the existing pattern used in createBranch()/createFile(): read $status =
$response['status'], if $status is not in the expected 2xx range then
throw/return an error (include the response body/message) or call the same error
handling routine used elsewhere, otherwise return $response['body']; reference
the createPullRequest(), getPullRequest(), $response['status'] and
$response['body'] symbols and reuse the same guard logic already implemented for
createBranch()/createFile().
---
Nitpick comments:
In `@tests/VCS/Adapter/GiteaTest.php`:
- Around line 101-145: The testCommentWorkflow method currently only deletes the
created repository on the happy path; wrap the main test logic in a try/finally
so the cleanup always runs: declare repositoryName as you already do, then
enclose creation/assertions (calls to createRepository, createFile,
createBranch, createPullRequest, createComment, getComment, updateComment, etc.)
in a try block and call $this->vcsAdapter->deleteRepository(self::$owner,
$repositoryName) inside a finally block to ensure the repo is removed even on
failures.
- Around line 193-205: The test testGetCommentInvalidId currently only asserts
the return is a string allowing raw API errors; update it (and the similar tests
around the other block) to assert a single concrete contract for the "not found"
case: either assertSame('', $result) if adapter should return an empty string,
or change the test to expectException(...) if the adapter should throw; locate
and modify the call to getComment in testGetCommentInvalidId (and the analogous
tests) and replace the loose assertIsString/assertIsArray with a specific
assertion matching the adapter's intended behavior, keeping
createRepository/createFile/deleteRepository setup/teardown intact.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: f8ed472e-7adc-479f-84ea-6a2939c54353
📒 Files selected for processing (2)
src/VCS/Adapter/Git/Gitea.phptests/VCS/Adapter/GiteaTest.php
- Add HTTP status checks to createPullRequest and getPullRequest - Add try/finally blocks to tests for proper cleanup on failures - Make error test assertions concrete (empty string or exception) - Improve testGetPullRequestWithInvalidNumber to use try/finally Note: Issue utopia-php#1 (adding branch parameter to abstract Git::createFile) requires architectural decision - will address after maintainer feedback
Meldiron
approved these changes
Mar 16, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds Gitea adapter support for pull-request and pull-request-comment workflows, and expands the Gitea test suite to cover those new endpoints end-to-end.
Changes:
- Add Gitea API methods to create PRs, fetch PR details, and locate an open PR by source branch.
- Implement PR comment create/get/update endpoints for Gitea.
- Update
createFileto optionally target a specific branch and add integration tests covering PR + comment workflows and error cases.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
src/VCS/Adapter/Git/Gitea.php |
Adds PR/comment endpoints and extends file creation with an optional branch payload field. |
tests/VCS/Adapter/GiteaTest.php |
Adds integration tests for PR and comment workflows, plus invalid-input scenarios. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
jaysomani
force-pushed
the
feat/gitea-pull-request-endpoints
branch
from
51603f0 to
3bb14cb
Compare
Meldiron
added
test
Meldiron
reviewed
Mar 18, 2026
Meldiron
reviewed
Mar 18, 2026
Meldiron
reviewed
Mar 18, 2026
Meldiron
approved these changes
Mar 18, 2026
Co-authored-by: Matej Bačo <matejbaco2000@gmail.com>
Meldiron
added
test
Greptile SummaryThis PR implements Gitea pull request and comment management endpoints ( Key issues found:
Confidence Score: 3/5
Important Files Changed
Last reviewed commit: "Apply suggestions fr..." |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Meldiron
added
test
Meldiron
added
test
Meldiron
approved these changes
Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tests: 7 new tests, all passing
Summary by CodeRabbit
New Features
Tests