Feature: Refactor DC Outer Loops creation #1144
Merged
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
vmouradian
force-pushed
the
feature/refactor-outer-loops
branch
2 times, most recently
from
822e54b to
5b602bd
Compare
vmouradian
changed the title
vmouradian
force-pushed
the
feature/refactor-outer-loops
branch
from
ef819c4 to
5d88652
Compare
vmouradian
changed the title
vmouradian
changed the base branch from
feature/contingency-parameters-extension
to
main
vmouradian
changed the base branch from
main
to
feature/contingency-parameters-extension
vmouradian
changed the title
vmouradian
changed the title
vmouradian
force-pushed
the
feature/refactor-outer-loops
branch
from
5d88652 to
1a417ae
Compare
vmouradian
merged commit 1a417ae
into
feature/contingency-parameters-extension
4 of 6 checks passed
vmouradian
force-pushed
the
feature/contingency-parameters-extension
branch
from
d47e484 to
69fe35c
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.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
Part of #1091 + adds consistency (imo)
What kind of change does this PR introduce?
Feature
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information: