Merge branch 'cmarinbe-2024-patches-patch-37765' into '2024-patches'
1 unresolved thread
1 unresolved thread
Add 2024-patches to CONTRIBUTING.md
See merge request !4526 (merged)
(cherry picked from commit c5ac94d0)
d7bbe06d Add 2024-patches to CONTRIBUTING.md c6a5241d add simulation use-case in master branch
Merge request reports
Activity
Filter activity
added Documentation label
assigned to @clemenci
added RTA label
Please, do not merge it. It will get into master via !4546 (merged)
fine with me and sorry I had missed it was included in !4546 (merged)
shall we close this to avoid future confusion?
I left it open because I wanted to see how merging !4546 (merged) was going to affect this.
Now I know that Gitlab correctly reports that this MR does not introduce any change in master (as the changes are already there), but it doesn't flag it as implicitly merged.
Please register or sign in to reply