DDO-4314 attempt oidc upgrade #927
Open
Conversation
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
|
|
No API changes detected |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #927 +/- ##
=======================================
Coverage 60.97% 60.97%
=======================================
Files 302 302
Lines 17181 17181
=======================================
Hits 10476 10476
Misses 5895 5895
Partials 810 810 🚀 New features to boost your workflow:
|
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.
Description
Include a short 1-5 sentence description of what your PR does and why.
This section should be as short as possible while still effectively communicating the intent behind the PR.
This can be omitted if the PR’s headline is clear enough, and change scope is limited.
If you need more than a paragraph, add it in a separate section called Background or Motivation.
Testing [required]
Describe how the changes have been tested.
Include screenshots where applicable to assist reviewers.
Risk Assessment [recommended]
What are the risks associated with deploying this change(if any)?
Can it be easily reverted in the event of unanticipated problems?
If not, what alternative solutions are there?