Skip to content

Setup enricher and new database backups #11

Setup enricher and new database backups

Setup enricher and new database backups #11

Triggered via push July 11, 2024 23:16
Status Success
Total duration 41s
Artifacts

backend.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
build
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build: Backend/FightCore.Repositories/Base/BaseRepository.cs#L26
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build: Backend/FightCore.Repositories/Base/BaseRepository.cs#L9
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build: Backend/FightCore.Repositories/MoveRepository.cs#L9
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build: Backend/FightCore.Repositories/MoveRepository.cs#L20
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build: Backend/FightCore.Services/MoveService.cs#L9
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build: Backend/FightCore.Services/MoveService.cs#L20
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build: Backend/FightCore.Enricher/Program.cs#L28
Dereference of a possibly null reference.
build: Backend/FightCore.Exporters/Program.cs#L60
'Character.FightCoreId' is obsolete
build: Backend/FightCore.Exporters/Program.cs#L39
Possible null reference argument for parameter 'folder' in 'Task Exporter.Export(IEnumerable toExport, string folder, string name)'.
build: Backend/FightCore.Api/Controllers/ExportController.cs#L38
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.