[releng] Improve error reporting in check-labels.js

Signed-off-by: Pierre-Charles David <pierre-charles.david@obeo.fr>

Author: pcdavid

CHANGELOG.adoc

@@ -36,6 +36,8 @@ As a result, the following GraphQL mutations have been removed `exposeRequiremen
 === Improvements
 
 - https://github.com/eclipse-syson/syson/issues/1583[#1583] [diagrams] Improve support for `Stakeholder`.
+On `Requirement` or `Concern` (either definition or usage) graphical nodes it is now possible to create new _stakeholders_ (which must reference existing `PartUsage`).
+Stakeholders are by default represented with a dedicated graphical node connected to the parent graphical node, or can appear inside the `stakeholders` list compartment.
 
 === New features
 

backend/views/syson-diagram-common-view/src/main/java/org/eclipse/syson/diagram/common/view/services/ViewToolService.java

@@ -256,13 +256,13 @@ public Element reconnectSourceNestedStakeholderEdge(Element self, Element newSou
             if (otherEnd.getOwningMembership() instanceof StakeholderMembership stakeholderMembership) {
                 newSource.getOwnedRelationship().add(stakeholderMembership);
             } else {
-                // This is an error, an Stakeholder should always be contained in an StakeholderMembership.
-                String errorMessage = "Cannot reconnect the Stakeholder, it is not owned by an " + StakeholderMembership.class.getSimpleName();
+                // This is an error, a Stakeholder should always be contained in a StakeholderMembership.
+                String errorMessage = "Cannot reconnect the Stakeholder, it is not owned by a " + StakeholderMembership.class.getSimpleName();
                 this.logger.error(errorMessage);
                 this.feedbackMessageService.addFeedbackMessage(new Message(errorMessage, MessageLevel.ERROR));
             }
         } else {
-            String errorMessage = "Cannot reconnect an Stakeholder to non-Requirement element";
+            String errorMessage = "Cannot reconnect a Stakeholder to a non-Requirement element";
             this.logger.warn(errorMessage);
             this.feedbackMessageService.addFeedbackMessage(new Message(errorMessage, MessageLevel.WARNING));
         }

doc/content/modules/user-manual/assets/images/release-notes-stakeholder-menu.png

@@ -25,6 +25,12 @@
 ** Add tools to create timeslices and snapshots, available on `OccurrenceUsage`, `ItemUsage`, and `PartUsage` graphical nodes.
 These tools leverage a selection dialog to either create a specific timeslice/snapshot graphical node or, if no selection is made, default to a timeslice/snapshot `OccurrenceUsage` graphical node.
 ** Improved support for `Stakeholder`.
+On `Requirement` or `Concern` (either definition or usage) graphical nodes it is now possible to create new _stakeholders_ (which must reference existing `PartUsage`).
+Stakeholders are by default represented with a dedicated graphical node connected to the parent graphical node, or can appear inside the `stakeholders` list compartment.
+
+image::release-notes-stakeholder-menu.png[Tool to create a new Stakeholder]
+
+image::release-notes-stakeholder-node.png[Default representation of Stakeholder connected to its corresponding `RequirementDefinition`]
 
 == Technical details
 

doc/content/modules/user-manual/assets/images/release-notes-stakeholder-node.png

@@ -1,5 +1,5 @@
 /*******************************************************************************
- * Copyright (c) 2023 Obeo.
+ * Copyright (c) 2023, 2026 Obeo.
  * This program and the accompanying materials
  * are made available under the terms of the Eclipse Public License v2.0
  * which accompanies this distribution, and is available at
@@ -12,23 +12,24 @@
  *******************************************************************************/
 const event = process.env.GITHUB_EVENT;
 const body = JSON.parse(event);
+const labels = body.pull_request.labels;
 
-const hasOnePriorityLabel =
-  body.pull_request.labels.filter((label) => label.name.startsWith('priority:'))
-    .length === 1;
-const hasOneReviewLabel =
-  body.pull_request.labels.filter((label) =>
-    label.name.startsWith('pr: to review')
-  ).length === 1;
-
-if (!hasOnePriorityLabel || !hasOneReviewLabel) {
-  console.log(
-    'The pull request is either lacking the priority or the pr label'
-  );
-  process.exit(1);
-} else if (body.pull_request.labels.length > 2) {
-  console.log(
-    'The pull request contains useless labels, please use priority and pr labels for pull requests'
+const errors = [];
+if (labels.filter((label) => label.name.startsWith("priority:")).length !== 1) {
+  errors.push("The pull request must have exactly one 'priority:' label");
+}
+if (
+  labels.filter((label) => label.name.startsWith("pr: to review")).length !== 1
+) {
+  errors.push("The pull request must have exactly one 'pr: to review' label");
+}
+if (labels.length > 2) {
+  errors.push(
+    "The pull request contains useless labels, please use only priority and pr labels for pull requests",
   );
+}
+
+if (errors.length > 0) {
+  errors.map((message) => console.log(message));
   process.exit(1);
 }