Skip to content

Conversation

@mcharfadi
Copy link
Contributor

@mcharfadi mcharfadi commented Jan 5, 2026

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.

@mcharfadi mcharfadi added this to the 2026.1.0 milestone Jan 5, 2026
@mcharfadi mcharfadi requested a review from AxelRICHARD January 5, 2026 10:43
@mcharfadi mcharfadi linked an issue Jan 5, 2026 that may be closed by this pull request
@mcharfadi mcharfadi force-pushed the mch/enh/port-usage-item-compartment branch 6 times, most recently from 9a151e0 to 4852d5d Compare January 5, 2026 11:25
@mcharfadi mcharfadi marked this pull request as ready for review January 5, 2026 12:05
@mcharfadi mcharfadi force-pushed the mch/enh/port-usage-item-compartment branch 4 times, most recently from 7f27f83 to a6f4a9a Compare January 7, 2026 08:16
@AxelRICHARD AxelRICHARD force-pushed the mch/enh/port-usage-item-compartment branch from a6f4a9a to 3e38319 Compare January 7, 2026 14:06
Bug: #1772
Signed-off-by: Michaël Charfadi <michael.charfadi@obeosoft.com>
@AxelRICHARD AxelRICHARD force-pushed the mch/enh/port-usage-item-compartment branch from 3e38319 to 54f3473 Compare January 7, 2026 14:09
@AxelRICHARD AxelRICHARD merged commit 1d645f9 into main Jan 7, 2026
4 checks passed
@AxelRICHARD AxelRICHARD deleted the mch/enh/port-usage-item-compartment branch January 7, 2026 16:13
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.

Add "items" list compartment on PortUsage nodes.

3 participants