Skip to content

[2208] Fix the edge connection tool targeting standard library element - #2455

Open
gcoutable wants to merge 1 commit into
mainfrom
gco/fix/connection-to-standard-library-element
Open

[2208] Fix the edge connection tool targeting standard library element#2455
gcoutable wants to merge 1 commit into
mainfrom
gco/fix/connection-to-standard-library-element

Conversation

@gcoutable

@gcoutable gcoutable commented Aug 21, 2026

Copy link
Copy Markdown
Member

Bug: #2208
Signed-off-by: Guillaume Coutable guillaume.coutable@obeo.fr

PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW

Auto review

  • Have you reviewed this PR? Please do a first quick review, It is very useful to detect typos and missing copyrights, check comments, check your code... The reviewer will thank you for that :)

Project management

  • Has the pull request been added to the relevant milestone?
  • Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
  • Have the relevant issues been added to the pull request?
  • Have the relevant labels been added to the issues? (area:, type:)
  • Have the relevant issues been added to the same project milestone as the pull request?

Changelog and release notes

  • Has the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc been updated to reference the relevant issues?
  • Have the relevant API breaks been described in the CHANGELOG.adoc?
  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
  • In case of a change with a visual impact, are there any screenshots in the doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
  • In case of a key change, has the change been added to Key highlights section in doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?

Documentation

  • Have you included an update of the documentation in your pull request? Please ask yourself if an update (installation manual, user manual, developer manual...) is needed and add one accordingly.

Tests

  • Is the code properly tested? Any pull request (fix, enhancement or new feature) should come with a test (or several). It could be unit tests, integration tests or cypress tests depending on the context. Only doc and releng pull request do not need for tests.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes contain new ActionUsage elements, a done ActionUsage and the result of all migration participants until now.

@gcoutable
gcoutable force-pushed the gco/fix/connection-to-standard-library-element branch from 49cacc6 to dfd5af7 Compare August 21, 2026 09:25
@gcoutable
gcoutable marked this pull request as ready for review August 21, 2026 09:28
@gcoutable
gcoutable requested a review from AxelRICHARD August 21, 2026 09:28
Bug: #2208
Signed-off-by: Guillaume Coutable <guillaume.coutable@obeo.fr>
@AxelRICHARD
AxelRICHARD force-pushed the gco/fix/connection-to-standard-library-element branch from dfd5af7 to d73a50f Compare August 21, 2026 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

New Connection is not working when targeting the Done Action node

2 participants