From d707102958deda188ddd44f44854dab25394eadb Mon Sep 17 00:00:00 2001
From: Kynan Ware <47394200+BagToad@users.noreply.github.com>
Date: Thu, 15 Aug 2024 11:24:40 -0600
Subject: [PATCH] Add a note about external contributors to
 `working-with-us.md`

---
 docs/working-with-us.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/working-with-us.md b/docs/working-with-us.md
index b4163350b0c..38326921eac 100644
--- a/docs/working-with-us.md
+++ b/docs/working-with-us.md
@@ -4,6 +4,9 @@ POV: your team at GitHub is interested in shipping a new command in `gh`.
 
 This document outlines the process the CLI team prefers for helping ensure success both for your new feature and the CLI project as a whole.
 
+> [!NOTE]
+> External contributors, please see [CONTRIBUTING.md](/.github/CONTRIBUTING.md).
+
 ## Step 0: Create an extension
 
 Even if you want to see your code merged into `gh`, you should start with [an extension](https://docs.github.com/en/github-cli/github-cli/creating-github-cli-extensions) written in Go and leveraging [go-gh](https://github.com/cli/go-gh). Though `gh` extensions can be written in any language, we treat Go as a first class experience and ship a library of helpers for extensions written in Go.