-
Notifications
You must be signed in to change notification settings - Fork 333
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
[JTC] Remove start_with_holding
option
#839
[JTC] Remove start_with_holding
option
#839
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #839 +/- ##
==========================================
- Coverage 47.22% 46.74% -0.49%
==========================================
Files 40 40
Lines 3636 3635 -1
Branches 1716 1715 -1
==========================================
- Hits 1717 1699 -18
- Misses 735 749 +14
- Partials 1184 1187 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This pull request is in conflict. Could you fix it @christophfroehlich? |
a4e8e9c
to
29953b2
Compare
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
(cherry picked from commit 62ce487)
(cherry picked from commit 62ce487)
(cherry picked from commit 62ce487)
(cherry picked from commit 62ce487)
(cherry picked from commit 62ce487)
(cherry picked from commit 62ce487)
(cherry picked from commit 62ce487)
It now always holds. Closes #816
It was there already since August/4 releases. Should we deprecate it first? I don't think so, like this we will get earlier feedback if someone really needs this (what we didn't think about).