From 307f0c789a5b7350d94938375d7259046b6897b2 Mon Sep 17 00:00:00 2001
From: Jonathan Nagayoshi <jonathan@nagayoshi.com.br>
Date: Mon, 27 Nov 2023 10:45:50 -0300
Subject: [PATCH] docs: adds open in devcontainer badge

---
 README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.md b/README.md
index 3489804..76266ea 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,11 @@
 <p align="center">
   <a href="https://github.com/sonikro/aws-run/actions"><img alt="aws-run-action status" src="https://github.com/sonikro/aws-run/workflows/build-test/badge.svg"></a>
+
 </p>
 
+[![Open in Dev Containers](https://img.shields.io/static/v1?label=Dev%20Containers&message=Open&color=blue&logo=visualstudiocode)](https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/sonikro/aws-run)
+
+
 # Run code remotely in your AWS Account with GitHub Actions
 
 This action allows you to run a script inside of your AWS Account, without having to spin up your own runner. By leveraging the power of ECS Tasks, you can use any docker image, and run any script inside of your Job, as if that script was being executed inside of the runner, however, the script is remotely executed inside of your AWS VPC, which grants your step special access to private resources, such as RDS Databases, Internal Loadbalancers, and much more.