-
Notifications
You must be signed in to change notification settings - Fork 4
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
Replace rao elementary action by core action #920
Draft
pjeanmarie
wants to merge
12
commits into
main
Choose a base branch
from
replace_rao_elementary_action_by_core_action
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
pjeanmarie
force-pushed
the
replace_rao_elementary_action_by_core_action
branch
2 times, most recently
from
March 11, 2024 17:15
0ff2a6c
to
518b0c3
Compare
pjeanmarie
force-pushed
the
replace_rao_elementary_action_by_core_action
branch
2 times, most recently
from
March 19, 2024 08:48
381dfda
to
1b2ca89
Compare
pjeanmarie
force-pushed
the
replace_rao_elementary_action_by_core_action
branch
4 times, most recently
from
April 2, 2024 13:27
e3881fe
to
6ee0599
Compare
pjeanmarie
force-pushed
the
replace_rao_elementary_action_by_core_action
branch
2 times, most recently
from
April 10, 2024 09:31
1f76983
to
8ef8af4
Compare
pjeanmarie
force-pushed
the
replace_rao_elementary_action_by_core_action
branch
4 times, most recently
from
April 23, 2024 13:49
53b9e7d
to
af0a91b
Compare
pjeanmarie
force-pushed
the
replace_rao_elementary_action_by_core_action
branch
9 times, most recently
from
May 7, 2024 08:42
2787a91
to
b03ec03
Compare
pjeanmarie
force-pushed
the
replace_rao_elementary_action_by_core_action
branch
from
May 13, 2024 16:30
b03ec03
to
4b627de
Compare
pjeanmarie
force-pushed
the
replace_rao_elementary_action_by_core_action
branch
6 times, most recently
from
May 17, 2024 15:20
8e0e299
to
fdefc4a
Compare
pjeanmarie
force-pushed
the
replace_rao_elementary_action_by_core_action
branch
2 times, most recently
from
May 23, 2024 08:21
53c3a8d
to
5d25c0a
Compare
pjeanmarie
force-pushed
the
replace_rao_elementary_action_by_core_action
branch
from
May 31, 2024 17:35
5d25c0a
to
e71e572
Compare
pjeanmarie
changed the title
WIP: Replace rao elementary action by core action
Replace rao elementary action by core action
Jun 5, 2024
pjeanmarie
added
the
PR : pending-for-dependency-release
This PR can't be merged until one dependency is updated
label
Jun 5, 2024
Do not merge: Need next core version (6.4.0), then pom need to be updated (6.4.0-SNAPSHOT -> 6.4.0) and changes on CI files need to be removed. |
pjeanmarie
force-pushed
the
replace_rao_elementary_action_by_core_action
branch
from
June 5, 2024 08:42
e71e572
to
307c918
Compare
7 tasks
…ial action modification Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
- PR7 and PR17 had actions of type A05 done on generator (and not load), it should be type A04 - PR17 had action B24 done on switch (not transformer), it should be A07 Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
pjeanmarie
force-pushed
the
replace_rao_elementary_action_by_core_action
branch
from
June 7, 2024 15:47
307c918
to
7ea95f7
Compare
Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
…n apply as a first step to replace rao action by core action Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
…on, so they are moved out of elementary action Remove network elements from elementary action since core remedial action do not have network element(s) Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
…ompiles) Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
…ir tests (not cucumber) Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
…cucumber tests which verified the type of elementary actions Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
…bility test and exhaustive crac creation test Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
pjeanmarie
force-pushed
the
replace_rao_elementary_action_by_core_action
branch
from
June 10, 2024 15:53
7ea95f7
to
f7a1e93
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking-change
Changes could break users' code
PR : pending-for-dependency-release
This PR can't be merged until one dependency is updated
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?
What kind of change does this PR introduce?
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: