From d0e60a483b7caf45eec4cc973c832b454865fece Mon Sep 17 00:00:00 2001
From: Jonathan Yu <jawnsy@cpan.org>
Date: Sun, 19 Dec 2021 00:25:47 +0000
Subject: [PATCH 1/3] chore: add configuration for Semantic Pull Requests app

---
 .github/semantic.yaml | 59 +++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 59 insertions(+)
 create mode 100644 .github/semantic.yaml

diff --git a/.github/semantic.yaml b/.github/semantic.yaml
new file mode 100644
index 000000000000..728e9de0e0ce
--- /dev/null
+++ b/.github/semantic.yaml
@@ -0,0 +1,59 @@
+###############################################################################
+# This file configures "Semantic Pull Requests", which is documented here:
+# https://github.com/zeke/semantic-pull-requests
+###############################################################################
+
+# Scopes are optionally supplied after a 'type'. For example, in
+#
+# feat(cdr): autostart ui
+#
+# '(cdr)' is the scope. Scopes are used to signify where the change occurred.
+scopes: []
+
+# We only check that the PR title is semantic. The PR title is automatically
+# applied to the "Squash & Merge" flow as the suggested commit message, so this
+# should suffice unless someone drastically alters the message in that flow.
+titleOnly: true
+
+# Types are the 'tag' types in a commit or PR title. For example, in
+#
+# chore: fix thing
+#
+# 'chore' is the type.
+types:
+  # A build of any kind.
+  - build
+
+  # A RELEASED fix that will NOT be back-ported. The originating issue may have
+  # been discovered internally or externally to Coder.
+  - fix
+
+  # Any code task that is ignored for changelog purposes. Examples include
+  # devbin scripts and internal-only configurations.
+  - chore
+
+  # Any work performed on CI.
+  - ci
+
+  # An UNRELEASED correction. For example, features are often built
+  # incrementally and sometimes introduce minor flaws during a release cycle.
+  # Corrections address those increments and flaws.
+  - correct
+
+  # Work that directly implements or supports the implementation of a feature.
+  - feat
+
+  # A fix for a RELEASED bug (regression fix) that is intended for patch-release
+  # purposes.
+  - hotfix
+
+  # A refactor changes code structure without any behavioral change.
+  - refactor
+
+  # A git revert for any style of commit.
+  - revert
+
+  # Adding tests of any kind. Should be separate from feature or fix
+  # implementations. For example, if a commit adds a fix + test, it's a fix
+  # commit. If a commit is simply bumping coverage, it's a test commit.
+  - test

From 94f4516710baacfa6f9dd1c21f0a6178d8fa2d9e Mon Sep 17 00:00:00 2001
From: Jonathan Yu <jawnsy@cpan.org>
Date: Mon, 10 Jan 2022 20:34:43 +0000
Subject: [PATCH 2/3] update lists

---
 .github/semantic.yaml | 35 +++++++++++++++++++++--------------
 1 file changed, 21 insertions(+), 14 deletions(-)

diff --git a/.github/semantic.yaml b/.github/semantic.yaml
index 728e9de0e0ce..ad2486b052e1 100644
--- a/.github/semantic.yaml
+++ b/.github/semantic.yaml
@@ -5,10 +5,27 @@
 
 # Scopes are optionally supplied after a 'type'. For example, in
 #
-# feat(cdr): autostart ui
+# feat(docs): autostart ui
 #
-# '(cdr)' is the scope. Scopes are used to signify where the change occurred.
-scopes: []
+# '(docs)' is the scope. Scopes are used to signify where the change occurred.
+scopes:
+  # docs: changes to the code-server documentation.
+  - docs
+
+  # vendor: changes to vendored dependencies.
+  - vendor
+
+  # tests: changes to test code.
+  - tests
+
+  # deps: changes to code-server's dependencies.
+  - deps
+
+  # cs: changes to code specific to code-server.
+  - cs
+
+  # cli: changes to the command-line interface.
+  - cli
 
 # We only check that the PR title is semantic. The PR title is automatically
 # applied to the "Squash & Merge" flow as the suggested commit message, so this
@@ -24,8 +41,7 @@ types:
   # A build of any kind.
   - build
 
-  # A RELEASED fix that will NOT be back-ported. The originating issue may have
-  # been discovered internally or externally to Coder.
+  # A user-facing change that corrects a defect in code-server.
   - fix
 
   # Any code task that is ignored for changelog purposes. Examples include
@@ -35,18 +51,9 @@ types:
   # Any work performed on CI.
   - ci
 
-  # An UNRELEASED correction. For example, features are often built
-  # incrementally and sometimes introduce minor flaws during a release cycle.
-  # Corrections address those increments and flaws.
-  - correct
-
   # Work that directly implements or supports the implementation of a feature.
   - feat
 
-  # A fix for a RELEASED bug (regression fix) that is intended for patch-release
-  # purposes.
-  - hotfix
-
   # A refactor changes code structure without any behavioral change.
   - refactor
 

From 5713508746463d71d422979a9b978b8ed09c6c1b Mon Sep 17 00:00:00 2001
From: Jonathan Yu <jawnsy@cpan.org>
Date: Mon, 10 Jan 2022 20:55:47 +0000
Subject: [PATCH 3/3] remove tests scope

---
 .github/semantic.yaml | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/.github/semantic.yaml b/.github/semantic.yaml
index ad2486b052e1..27a663ed5662 100644
--- a/.github/semantic.yaml
+++ b/.github/semantic.yaml
@@ -15,9 +15,6 @@ scopes:
   # vendor: changes to vendored dependencies.
   - vendor
 
-  # tests: changes to test code.
-  - tests
-
   # deps: changes to code-server's dependencies.
   - deps