From cc64872902fc570e8a49858509714284f9e0ab99 Mon Sep 17 00:00:00 2001
From: GitHub Teacher <2132216+githubteacher@users.noreply.github.com>
Date: Tue, 16 Apr 2019 16:19:59 +0200
Subject: [PATCH] add information and resources on choosing a workflow

---
 workflows/README.md | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 workflows/README.md

diff --git a/workflows/README.md b/workflows/README.md
new file mode 100644
index 0000000..444ff1a
--- /dev/null
+++ b/workflows/README.md
@@ -0,0 +1,8 @@
+## Workflows & Branching Strategies 
+
+There's no one perfect workflow or branching strategy that fits every project. However, when you're collaborating in a repository on GitHub, it's important to have a clear workflow outlined and communicated. That way, contributors know what to expect and how to get things done. 
+
+Here are a few of our favorite resources to help you make the right choice for your project: 
+- [The GitHub Flow](https://guides.github.com/introduction/flow/)
+- [Azure's Guide to Branching Strategies](https://docs.microsoft.com/en-us/azure/devops/repos/git/git-branching-guidance?view=azure-devops)
+- A list of awesome [Contributing guides](https://github.com/mntnr/awesome-contributing) won't necessarily help you decide on a workflow, but it will help you decide how to communicate your chosen workflow