This is an automated email from the ASF dual-hosted git repository. dahn pushed a change to branch healthcheck-4.20 in repository https://gitbox.apache.org/repos/asf/cloudstack.git
discard e2894decd1c Merge branch '4.20' of https://github.com/apache/cloudstack into healthcheck-4.20 discard 4d32e45a6dd Merge branch '4.20' of https://github.com/apache/cloudstack into healthcheck-4.20 discard 07a5a055b91 Merge branch '4.20' of https://github.com/apache/cloudstack into healthcheck-4.20 discard 6474e8a48a2 Merge branch '4.20' into healthcheck-4.20 discard bea9e6ead7c Merge branch '4.20' of https://github.com/apache/cloudstack into healthcheck-4.20 discard 2e7491a699f 4.20 Health Check, please don't merge this! add f2a6a2ff131 .github: fix sonar checks (#10894) add aed009edf62 4.20 Health Check, please don't merge this! This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (e2894decd1c) \ N -- N -- N refs/heads/healthcheck-4.20 (aed009edf62) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: .github/workflows/main-sonar-check.yml | 2 +- .github/workflows/sonar-check.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
