fix(codeberg): apply reviewers after PR create (#367)#445
Merged
barrettruth merged 1 commit intomainfrom Apr 27, 2026
Merged
Conversation
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
1 participant
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.
Problem
Codeberg PR creation can carry labels, assignees, and milestones, but
tea pr createcannot set reviewers. That caused requested reviewers from Forge compose buffers to be dropped on create instead of being preserved.Solution
After a successful PR create, resolve the created PR from the explicit head branch and head scope, then apply reviewer diffs with the backend update command when the backend supports reviewer updates but not reviewer creation.
Part of #367.