From 76f2264a7c8728c923484baea6352b32024e90c1 Mon Sep 17 00:00:00 2001
From: Lukas Klingsbo <lukas.klingsbo@gmail.com>
Date: Mon, 7 Oct 2024 22:31:42 +0200
Subject: [PATCH] docs: Add link to the Melos GitHub action (#771)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!--
  Thanks for contributing!

Provide a description of your changes below and a general summary in the
title

Please look at the following checklist to ensure that your PR can be
accepted quickly:
-->

## Description

This just adds a link to the Melos GitHub action, so that more people
can find it.

## Type of Change

<!--- Put an `x` in all the boxes that apply: -->

- [ ] ✨ `feat` -- New feature (non-breaking change which adds
functionality)
- [ ] 🛠️ `fix` -- Bug fix (non-breaking change which fixes an issue)
- [ ] ❌ `!` -- Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] 🧹 `refactor` -- Code refactor
- [ ] ✅ `ci` -- Build configuration change
- [x] 📝 `docs` -- Documentation
- [ ] 🗑️ `chore` -- Chore
---
 packages/melos/README.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/packages/melos/README.md b/packages/melos/README.md
index 7a57e8d5..7b96f8a3 100644
--- a/packages/melos/README.md
+++ b/packages/melos/README.md
@@ -34,6 +34,13 @@ bases into multi-package repositories (sometimes called
 **Melos is a tool that optimizes the workflow around managing multi-package
 repositories with git and Pub.**
 
+## Github Action
+
+If you're planning on using Melos in your GitHub Actions workflows, you can use
+the [Melos Action](https://github.com/flame-engine/flame/tree/main/examples/assets/svgs)
+to run Melos commands, this action also supports automatic versioning and
+publishing directly from your workflows.
+
 ## What does a Melos workspace look like?
 
 A default file structure looks something like this: