Skip to content

Add capability for styling DocumentControl tabs #1059

Add capability for styling DocumentControl tabs

Add capability for styling DocumentControl tabs #1059

Triggered via pull request November 7, 2023 11:19
Status Failure
Total duration 3m 53s
Artifacts 1

build.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 2 warnings
build-mac: src/Eto/Forms/Controls/DocumentControl.cs#L24
Missing XML comment for publicly visible type or member 'DocumentPageClosingEventArgs'
build-mac: src/Eto/Forms/Controls/DocumentControl.cs#L24
Missing XML comment for publicly visible type or member 'DocumentPageClosingEventArgs'
build-mac: src/Eto/Forms/Controls/DocumentControl.cs#L24
Missing XML comment for publicly visible type or member 'DocumentPageClosingEventArgs'
build-mac
Process completed with exit code 1.
build-windows: src/Eto/Forms/Controls/DocumentControl.cs#L24
Missing XML comment for publicly visible type or member 'DocumentPageClosingEventArgs'
build-windows: src/Eto/Forms/Controls/DocumentControl.cs#L24
Missing XML comment for publicly visible type or member 'DocumentPageClosingEventArgs'
build-windows
Process completed with exit code 1.
build-mac
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, maxim-lobanov/setup-xamarin@v1, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-windows
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Artifacts

Produced during runtime
Name Size
log Expired
3.32 MB