Repository navigation
api: team names from the config - #169
Merged
Merged
Conversation
trick77
force-pushed
the
api-team-names-config
branch
from
November 19, 2026 08:25
a9dc80a to
74b8d4e
Compare
Deps.TeamNames and the teams handler sorted the configured teams themselves; config.Config.TeamNames already does.
trick77
force-pushed
the
api-team-names-config
branch
from
November 19, 2026 08:40
74b8d4e to
3ab0eb3
Compare
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.
Deps.TeamNames and the teams handler sorted the configured teams themselves; config.Config.TeamNames already does (same ascending string sort). TestTeams now checks both the picker's and the schedule's list against the harness config's teams.