[Refactor] Extract Azure DevOps credential validation - #916
Merged
brunobergher merged 2 commits intoJul 31, 2026
Conversation
Contributor
Author
brunobergher
marked this pull request as ready for review
July 31, 2026 09:29
brunobergher
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
July 31, 2026 09:29
brunobergher
approved these changes
Jul 31, 2026
brunobergher
approved these changes
Jul 31, 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
2 participants
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
Extracted Azure DevOps credential acquisition, delegated token refresh, credential probing, validation results, and rejection-message formatting into a credential-owned module. Existing package exports remain available through the API entry point, and focused credential tests now cover the subsystem independently.
Why this change was made
Credential behavior had become a large, separate concern inside the broad Azure DevOps API module. Giving it a cohesive owner reduces the API module's scope and makes authentication changes easier to review and test without touching repository, comment, hook, or sync code.
Impact
There is no intended user-facing behavior change. Azure DevOps configuration and web consumers retain the same public contracts while credential behavior gains a focused maintenance and test boundary.