WIP

README.md

@@ -1,6 +1,6 @@
 # Serilog.Sinks.Http - Sample in .NET Core
 
-[![Build status](https://ci.appveyor.com/api/projects/status/n6xpr0vxexlb1oro/branch/master?svg=true)](https://ci.appveyor.com/project/FantasticFiasco/serilog-sinks-http-sample-dotnet-core/branch/master)
+[![CI](https://github.com/FantasticFiasco/serilog-sinks-http-sample-dotnet-core/actions/workflows/ci.yml/badge.svg)](https://github.com/FantasticFiasco/serilog-sinks-http-sample-dotnet-core/actions/workflows/ci.yml)
 
 This repository contains a sample application of [Serilog.Sinks.Http](https://github.com/FantasticFiasco/serilog-sinks-http) producing log events sent over HTTP to a basic log server.
 
@@ -15,4 +15,4 @@ What you will end up with is two containers, one producing log events while the
 ## Remarks
 
 - The sample application is using a custom implementation of a HTTP client, mainly to show that it is possible to do so. But don't specify a custom implementation if you don't have to.
-- The sink is configured in code, but could as well be configured in `appsettings.json` using [Serilog.Settings.Configuration](https://github.com/serilog/serilog-settings-configuration).
+- The sink is configured in code, but could as well be configured in `appsettings.json` using [Serilog.Settings.Configuration](https://github.com/serilog/serilog-settings-configuration).