From 4f41b7cc1b264f76d17524bd52d4f1a240a84cf6 Mon Sep 17 00:00:00 2001
From: Barb Cutler <Barb Cutler>
Date: Mon, 20 Jul 2026 10:46:59 -0400
Subject: [PATCH 1/2] workflows setup

---
 .github/workflows/pr_title_check.yml | 20 ++++++++++++++++++++
 .github/workflows/release.yml        | 23 +++++++++++++++++++++++
 2 files changed, 43 insertions(+)
 create mode 100644 .github/workflows/pr_title_check.yml
 create mode 100644 .github/workflows/release.yml

diff --git a/.github/workflows/pr_title_check.yml b/.github/workflows/pr_title_check.yml
new file mode 100644
index 0000000..5bbd9ac
--- /dev/null
+++ b/.github/workflows/pr_title_check.yml
@@ -0,0 +1,20 @@
+name: 'Submitty PR Title Check'
+on:
+  pull_request:
+    # check when PR
+    # * is created,
+    # * title is edited, and
+    # * new commits are added (to ensure failing title blocks merging)
+    types: [opened, reopened, edited, synchronize]
+
+jobs:
+  title-check:
+    runs-on: ubuntu-latest
+    steps:
+      #
+      # pull request titles format rules here:
+      # https://submitty.org/developer/how_to_contribute#how-to-make-a-pull-request-pr-to-submitty
+      #
+      # [<TYPE>:<MODULE>] <SUBJECT>
+      #
+      - uses: submitty/action-pr-title@main
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
new file mode 100644
index 0000000..406a0e0
--- /dev/null
+++ b/.github/workflows/release.yml
@@ -0,0 +1,23 @@
+name: Release
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  dispatch-update:
+    name: Dispatch Update
+    runs-on: ubuntu-latest
+    steps:
+      - uses: Submitty/peter-evans-repository-dispatch@v26.07.00
+        if: ${{ github.repository_owner == 'Submitty' }}
+        with:
+          event-type: repo-release
+          token: ${{ secrets.SUBMITTYBOT_DEPENDENCY_TOKEN }}
+          repository: ${{ github.repository_owner }}/Submitty
+          client-payload: '{
+              "repo_name": ${{ toJSON(github.event.repository.name) }},
+              "repo": ${{ toJSON(github.event.repository.full_name) }},
+              "tag": ${{ toJSON(github.event.release.tag_name) }}
+            }'
+

From 5e03a321181c25e0d2c07b270e3746dfd5a2b60e Mon Sep 17 00:00:00 2001
From: Barb Cutler <Barb Cutler>
Date: Mon, 20 Jul 2026 10:51:45 -0400
Subject: [PATCH 2/2] adding pull request template

---
 .github/PULL_REQUEST_TEMPLATE.md | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100755 .github/PULL_REQUEST_TEMPLATE.md

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100755
index 0000000..7008854
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,28 @@
+<!-- ** Please remove all comment blocks in the description before submitting this PR. ** -->
+
+<!-- NOTE: Please ensure your title and description align with Submitty conventions (see 
+https://submitty.org/developer/getting_started/make_a_pull_request for more details). 
+Each title has a prefix, and a limit of 40 chars. A description template has been 
+provided and must be completed in full. Please also ensure that all CI tests 
+are passing. Pull requests that do not meet these requirements are ineligible for 
+review and may be closed. -->
+
+### Why is this Change Important & Necessary?
+<!-- Include any GitHub issue that is fixed/closed using "Fixes #<number>" or "Closes #<number>" syntax.  
+Alternately write "Partially addresses #<number>" or "Related to #<number>" as appropriate. -->
+
+### What is the New Behavior?
+<!-- Include before & after screenshots/videos if the user interface has changed. -->
+
+### What steps should a reviewer take to reproduce or test the bug or new feature?
+
+### Automated Testing & Documentation
+<!-- Is this feature sufficiently tested by unit tests and end-to-end tests?  
+If this PR does not add/update the necessary automated tests, write a new GitHub issue and link it below.  
+Is this feature sufficiently documented on submitty.org?
+Link related PRs or new GitHub issue to update documentation. -->
+
+### Other information
+<!-- Is this a breaking change?  
+Does this PR include migrations to update existing installations?  
+Are there security concerns with this PR? -->