Annotations only rendered at the first modified file in a Pull Request

[tlohmar]

Problem description

With the new release automation tools, annotations are shown for any Error, Warning or Hint (GitHub Checks?). However, when multiple files are modified within a Pull Request, these annotations are only shown at the first file.

Expected action

Try to provide a consistent behavior.

Additional context

[rartych]

I think, the issue is related to https://github.com/camaraproject/tooling.

Anyway, it looks that it is the Github limitation:

10 warning annotations, 10 error annotations, and 10 notice annotations per step

You can see full result of validation by going to Actions tab in the Github for example: https://github.com/camaraproject/DedicatedNetworks/actions and clicking given (usually the latest) action run.

[tlohmar]

thx. Should I move the issue to tooling?

Anyway, I just wanted to raise awareness, as I was initially relying on the annotations and only a bit later realizing, that there are more warnings. Thus, these annotations are not as helpful as initially thought.

[rartych]

I am moving the issue to tooling.

Thanks for information,
After each correction the validation is re-run, new annotations should pop out, but indeed limited to 10, so it is not convenient.

[hdamker]

@tlohmar @rartych That is indeed a GH limitation ... and it is mainly impacting the migration phase towards Commonalities 0.8.0 where many APIs have these large numbers of warnings (errors are already ok). In steady state it is unlikely that a PR is creating more than 10 new warnings at the same time.

Hints are another topic, as they can pile up over time.

In general open for proposals how to address ... e.g. grouping the findings per file and code, and showing only the first occurrence in a file with a hint that there are more within the workflow summary listed (would keep more back than today, without some logic to will up the ten warnings finally).

[tlohmar]

@hdamker thanks for the clarification.

In general open for proposals how to address ...

• Do you have a collection of "known issues/aspects"? Could make sense that other developers are aware about that aspect.
• Maybe recommend to developers the usage of the PR verification output.
• Potentially even disable the annotations for the next release. Once M3 is reached, there should be a much lower number of Warnings & Hints.