From f6da00230b3450470ca249df090ae0da9b18aed4 Mon Sep 17 00:00:00 2001
From: Dale Wijnand <344610+dwijnand@users.noreply.github.com>
Date: Wed, 11 Apr 2018 15:43:01 +0100
Subject: [PATCH] Updated Good First Issues (markdown)

---
 Good-First-Issues.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Good-First-Issues.md b/Good-First-Issues.md
index 23bdf5c..69ffa89 100644
--- a/Good-First-Issues.md
+++ b/Good-First-Issues.md
@@ -20,7 +20,7 @@ To label an issue as a [good first issue][] is it must be:
 To convert an issue (e.g a [help wanted][] issue) so that it's ready for a new contributor do the following:
 
 1. get familiar with the issue, and some of the associated code/tests/docs
-2. make sure the issue template is followed (steps/problem/explanation/notes) so it's clear what is wrong and/or
+2. make sure the [issue template](https://raw.githubusercontent.com/sbt/sbt/1.x/ISSUE_TEMPLATE.md) is followed (steps/problem/explanation/notes) so it's clear what is wrong and/or
    what needs to be different
 3. make sure the issue is still valid, e.g the bug is reproducable
 4. make sure the purpose/relevance of the issue/change is clear (this helps motivate participation)