Skip to content

Refactor GetDetailsForTransaction complexity #325

Refactor GetDetailsForTransaction complexity

Refactor GetDetailsForTransaction complexity #325

Re-run triggered October 13, 2026 13:44
Status Success
Total duration 12m 56s
Artifacts 3

pullrequest.yml

on: pull_request
Build and Test Pull Requests
12m 49s
Build and Test Pull Requests
Fit to window
Zoom out
Zoom in

Annotations

21 warnings and 1 notice
Build and Test Pull Requests
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-dotnet@v4, actions/upload-artifact@v4, actions/upload-artifact@v4.4.0, dorny/test-reporter@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L215
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L210
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L195
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L185
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L156
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L129
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/SpecflowExtensions.cs#L132
Non-nullable property 'LineData' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/SpecflowExtensions.cs#L93
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/SpecflowExtensions.cs#L63
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

Artifacts

Produced during runtime
Name Size Digest
test-results
18.2 KB
sha256:120d0def69fad985661a6b1b4e25bc2014487384d84212c2627a4ced30d16aa1
tracelogs
262 KB
sha256:340329705f7c27b3f886058324952899c012d847f944a7654480044cf1daa189