[Fix] Gitea tasks use GitHub usernames for PR assignment - #1507
Open
roomote-roomote[bot] wants to merge 6 commits into
Open
[Fix] Gitea tasks use GitHub usernames for PR assignment#1507roomote-roomote[bot] wants to merge 6 commits into
roomote-roomote[bot] wants to merge 6 commits into
Conversation
Contributor
|
No new code issues found. See task
Reviewed 0d5f4db |
Contributor
Author
|
Fixed in |
daniel-lxs
marked this pull request as ready for review
August 21, 2026 20:12
daniel-lxs
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
August 21, 2026 20:12
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.
What changed
ALL_REPOSITORIEStasks without querying the aggregate sentinel as a repository.Why this change was made
Workspace-wide provider stamps can describe a primary repository rather than the repository receiving a pull request. Aggregate selections also need to retain their safe stamped attribution path without treating partial repository resolution as homogeneous.
Impact
PR attribution and assignment now follow the exact target repository provider and host, while fully resolved homogeneous all-repository tasks retain their linked provider identity. Ambiguous, incomplete, and mixed-provider selections fall back to Roomote attribution without a user assignee.