#7. Add status badge (#10)

Co-authored-by: maldworth <[email protected]>

readme.md

@@ -3,6 +3,13 @@ Sample Batch
 
 This sample will show a variety of built in tools and techniques in MassTransit.
 
+Build Status
+------------
+
+Branch | Status
+--- | :---:
+master | [![master](https://github.com/MassTransit/Sample-Batch/actions/workflows/dotnet.yml/badge.svg?branch=master)](https://github.com/MassTransit/Sample-Batch/actions/workflows/dotnet.yml)
+
 ## Requirements ##
 
 A message broker, and a database, and dotnet core. This sample provides a docker-compose.yml which uses RabbitMq (broker) and MsSql (db). If you are on windows, and have (LocalDb), and rabbitMq locally installed, you can skip the first step, but you will need to change the "ConnectionStrings" in the SampleBatch.Service appsettings.json.
@@ -40,4 +47,4 @@ My hope is to grow this sample over time, and introduce more documentation that
 - I wanted to show, you can link state machines with children using SQL and Foreign Keys. This might not be the best design for your system. It all depends on the domain boundaries of your "microservice". It just shows one possibility, if you know your sagas are tightly coupled. In this sample, I want the user to be able to see a history of Batches that were ran and the status of the jobs it processed.
 - The Sample allows RabbitMq or AzureSb to be used. All you do is add the config for the one you want, and on startup it will try to connect to the message broker that has config values present.
 - I'd like to perhaps expand the db to create an actual orderId entity, where the Cancel and Suspend Activities would actually use a DBContext and cancel them. Also maybe introduce a couple routing slip activities in sequence, to then show compensation.
-- Not too sure how I feel about the enum indicating what batch action to take, and then the switch statement in the ProcessJobConsumer where it conditionally creates the routingslip activity. Is there a more elegant way? I'll need to think about that.
+- Not too sure how I feel about the enum indicating what batch action to take, and then the switch statement in the ProcessJobConsumer where it conditionally creates the routingslip activity. Is there a more elegant way? I'll need to think about that.