Update README.md #25
cammurrayAnnotations
3 errors and 8 warnings
|
build-and-deploy
AADSTS700213: No matching federated identity record found for presented assertion subject 'repo:cammurray/ASTSync:ref:refs/heads/master'. Please check your federated identity credential Subject, Audience and Issuer against the presented assertion. https://docs.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation Trace ID: d71fa3ce-1773-4b8f-b340-159fda16c700 Correlation ID: 6721c717-3d75-4d5d-a766-02bec8783d2f Timestamp: 2024-05-30 02:28:49Z
|
|
build-and-deploy
Interactive authentication is needed. Please run:
az login
|
|
build-and-deploy
Login failed with Error: The process 'C:\Program Files\Microsoft SDKs\Azure\CLI2\wbin\az.cmd' failed with exit code 1. Double check if the 'auth-type' is correct. Refer to https://github.com/Azure/login#readme for more information.
|
|
build-and-deploy
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: azure/login@v1, actions/setup-dotnet@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
build-and-deploy
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-and-deploy
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
|
build-and-deploy:
Sync.cs#L267
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
build-and-deploy:
Sync.cs#L324
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
build-and-deploy
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
|
build-and-deploy:
Sync.cs#L267
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
build-and-deploy:
Sync.cs#L324
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|