This is an automated email from the ASF dual-hosted git repository. vishesh pushed a change to branch fix-vm-usage-history in repository https://gitbox.apache.org/repos/asf/cloudstack-go.git
discard 28c7fb8 Merge branch 'main' of https://github.com/apache/cloudstack-go into fix-vm-usage-history discard 74a5a52 Merge branch 'main' of https://github.com/apache/cloudstack-go into fix-vm-usage-history discard 818910e linting issue discard f89b2c7 Merge branch 'main' of https://github.com/apache/cloudstack-go into fix-vm-usage-history discard b471df6 Fix VM Usage histroy response add 3aaf3aa Fix userdatadetails add 1b6b293 Fix userdatadetails add d9394b2 Fix VM Usage histroy response add 3a9d038 linting issue add 4428802 generate code again after rebase 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 (28c7fb8) \ N -- N -- N refs/heads/fix-vm-usage-history (4428802) 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: cloudstack/AutoScaleService.go | 6 ++---- cloudstack/BackupService.go | 3 +-- cloudstack/VirtualMachineService.go | 9 +++------ cloudstack/VirtualNetworkFunctionsService.go | 3 +-- generate/generate.go | 2 ++ 5 files changed, 9 insertions(+), 14 deletions(-)
