Going secretless for Azure DevOps access #376
Draft
Conversation
This file contains 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
BillWagner
force-pushed
the
going-secretless
branch
2 times, most recently
from
cc35898
to
7411f20
Compare
BillWagner
force-pushed
the
going-secretless
branch
2 times, most recently
from
ce72ac9
to
23773dd
Compare
BillWagner
force-pushed
the
going-secretless
branch
3 times, most recently
from
09b5bf0
to
2641047
Compare
BillWagner
force-pushed
the
going-secretless
branch
2 times, most recently
from
e486e67
to
bfc561e
Compare
Update the SeQuester C# application to support secretless authentication.
Co-authored-by: David Pine <[email protected]>
BillWagner
force-pushed
the
going-secretless
branch
from
bfc561e
to
5ea6109
Compare
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.
First draft at using secretless authentication for Azure Dev Ops access.