[Fix] Mixed-provider environments fail to start - #1083
Closed
roomote-community[bot] wants to merge 3 commits into
Closed
[Fix] Mixed-provider environments fail to start#1083roomote-community[bot] wants to merge 3 commits into
roomote-community[bot] wants to merge 3 commits into
Conversation
Contributor
Author
|
1 issue outstanding. See task
Reviewed f89128f |
Contributor
Author
|
Superseded by the consolidated implementation in #1084. |
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
Why this change was made
Mixed-provider environments could be configured in the dashboard but failed during task bootstrap because token minting, repository setup, and source-control routing assumed a single provider for the whole workspace.
Impact
Tasks can prepare and operate on repositories from providers such as GitHub and GitLab in the same environment without broadening token scope or weakening unknown-repository validation. Legacy single-provider payloads retain their existing scalar, workspace-resolution, and default behavior.
Fixes #1082