From 83480cc3a5fd0bab0eddcb25739154ed168dbad5 Mon Sep 17 00:00:00 2001
From: Stoyan12314 <127962973+Stoyan12314@users.noreply.github.com>
Date: Wed, 22 Jan 2025 15:21:38 +0100
Subject: [PATCH] Chore: Advice for runners

Added advice which runner to use when
---
 research/Self-hosted-vs-Github-hosted.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/research/Self-hosted-vs-Github-hosted.md b/research/Self-hosted-vs-Github-hosted.md
index 9c9952c0..5d911c1e 100644
--- a/research/Self-hosted-vs-Github-hosted.md
+++ b/research/Self-hosted-vs-Github-hosted.md
@@ -40,6 +40,9 @@ Below are points which the types of runners are compared. The reason for choosin
   Ideal for large workloads or if an operating system not part of the ones which Github actions offers is needed. Self-hosted runners are great if the code base has processes that are very multithreaded. Additionally self-hosted runners are securer since they are running on the network of the user.(Medan, 2022, “Tips and recommendations for choosing the right runners”, ).
 
 
+## Advice
+
+GitHub-hosted runners are ideal for small teams like a startup developing a web application with straightforward workflows, while self-hosted runners offer the flexibility needed for complex, resource-intensive projects like an enterprise processing large datasets or running multithreaded processes that will benefit from customization and scalability of self-hosted runners.
 
 ---