-
Notifications
You must be signed in to change notification settings - Fork 23
Make STS destination port optional for CRR destinations #2698
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Issue: BB-733
Hello francoisferrand,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
... and 3 files with indirect coverage changes
@@ Coverage Diff @@
## development/9.1 #2698 +/- ##
===================================================
- Coverage 74.89% 74.65% -0.24%
===================================================
Files 200 200
Lines 13486 13488 +2
===================================================
- Hits 10100 10070 -30
- Misses 3376 3408 +32
Partials 10 10
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
delthas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Issue: BB-733
|
/approve |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue BB-733. Goodbye francoisferrand. The following options are set: approve |
We can use the transport (http or https) to compute a default port, so we don't need to patch the code in many places.
Issue: BB-733