Skip to content

✨ (WorkItemCloneCommand): add support for dynamic field value processing #172

✨ (WorkItemCloneCommand): add support for dynamic field value processing

✨ (WorkItemCloneCommand): add support for dynamic field value processing #172

Triggered via push July 29, 2024 10:05
Status Success
Total duration 1m 14s
Artifacts 1

main.yml

on: push
Setup & Configuration
10s
Setup & Configuration
Build & Test
40s
Build & Test
Release to GitHub Wiki
0s
Release to GitHub Wiki
Release to GitHub Releases
0s
Release to GitHub Releases
Fit to window
Zoom out
Zoom in

Annotations

14 warnings
Setup & Configuration
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Setup & Configuration
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build & Test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build & Test
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build & Test: AzureDevOps.WorkItemClone/DataContracts/WorkItemToBuildRelation.cs#L6
Non-nullable property 'rel' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build & Test: AzureDevOps.WorkItemClone/Authenticator.cs#L30
Non-nullable field 'application' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
Build & Test: AzureDevOps.WorkItemClone/DataContracts/WorkItemToBuild.cs#L9
Non-nullable property 'fields' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build & Test: AzureDevOps.WorkItemClone/DataContracts/WorkItemToBuild.cs#L10
Non-nullable property 'relations' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build & Test: AzureDevOps.WorkItemClone/DataContracts/WorkItemToBuild.cs#L12
Non-nullable property 'targetUrl' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build & Test: AzureDevOps.WorkItemClone/DataContracts/WorkItemToBuild.cs#L14
Non-nullable property 'workItemType' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build & Test: AzureDevOps.WorkItemClone/DataContracts/WorkItemAdd.cs#L42
Non-nullable property 'comment' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build & Test: AzureDevOps.WorkItemClone/DataContracts/WorkItemAdd.cs#L35
Non-nullable property 'rel' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build & Test: AzureDevOps.WorkItemClone/DataContracts/WorkItemAdd.cs#L36
Non-nullable property 'url' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build & Test: AzureDevOps.WorkItemClone/DataContracts/WorkItemAdd.cs#L37
Non-nullable property 'attributes' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Artifacts

Produced during runtime
Name Size
AzureDevOpsWorkItemClone
5.14 MB