From 6793ed5114f37f3c17a6a73a49a6ba23551609d9 Mon Sep 17 00:00:00 2001
From: Dasun Pubudumal <pubudumald@gmail.com>
Date: Mon, 17 Mar 2025 13:09:45 +0000
Subject: [PATCH 1/3] Refactor release version check workflow to use
 centralized configuration

---
 .github/workflows/check_release_version.yml | 20 ++------------------
 1 file changed, 2 insertions(+), 18 deletions(-)

diff --git a/.github/workflows/check_release_version.yml b/.github/workflows/check_release_version.yml
index 7bc27df..3ff8f7f 100644
--- a/.github/workflows/check_release_version.yml
+++ b/.github/workflows/check_release_version.yml
@@ -7,21 +7,5 @@ on:
       - main
 
 jobs:
-  check:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Get specific changed files
-        id: changed-files-specific
-        uses: tj-actions/changed-files@v41
-        with:
-          files: |
-            .release-version
-
-      - name: Run step looking for change in the release version
-        run: >-
-          if ! "${{ steps.changed-files-specific.outputs.any_changed }}"; then
-            echo "Please change the release version number"
-            exit 1;
-          fi
+  check-release-verion:
+    uses: sanger/.github/.github/workflows/check-release-version.yml@master

From c6540f609217cc4ae4818a56a71502a3f2e319c6 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Mon, 17 Mar 2025 15:35:05 +0000
Subject: [PATCH 2/3] Bump jinja2 from 3.1.5 to 3.1.6

Bumps [jinja2](https://github.com/pallets/jinja) from 3.1.5 to 3.1.6.
- [Release notes](https://github.com/pallets/jinja/releases)
- [Changelog](https://github.com/pallets/jinja/blob/main/CHANGES.rst)
- [Commits](https://github.com/pallets/jinja/compare/3.1.5...3.1.6)

---
updated-dependencies:
- dependency-name: jinja2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
---
 Pipfile.lock | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/Pipfile.lock b/Pipfile.lock
index 09cbad9..d14d9e0 100644
--- a/Pipfile.lock
+++ b/Pipfile.lock
@@ -296,11 +296,12 @@
         },
         "jinja2": {
             "hashes": [
-                "sha256:8fefff8dc3034e27bb80d67c671eb8a9bc424c0ef4c0826edbff304cceff43bb",
-                "sha256:aba0f4dc9ed8013c424088f68a5c226f7d6097ed89b246d7749c2ec4175c6adb"
+                "sha256:0137fb05990d35f1275a587e9aee6d56da821fc83491a0fb838183be43f66d6d",
+                "sha256:85ece4451f492d0c13c5dd7c13a64681a86afae63a5f347908daf103ce6d2f67"
             ],
+            "index": "pypi",
             "markers": "python_version >= '3.7'",
-            "version": "==3.1.5"
+            "version": "==3.1.6"
         },
         "mako": {
             "hashes": [

From 14bdb3c3cac7d2fb6e3e58537ac97f4bb72cef76 Mon Sep 17 00:00:00 2001
From: Tom Whiteley <tw6@sanger.ac.uk>
Date: Mon, 16 Mar 2026 14:39:01 +0000
Subject: [PATCH 3/3] Adding CONTRIBUTING.md

---
 CONTRIBUTING.md | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 CONTRIBUTING.md

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..03ce14d
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,30 @@
+# Contributing
+
+All contributions to this project are subject to the [MIT License](https://foss-haas.mit-license.org/). By submitting a contribution, you agree to license your work under these terms.
+
+## Contribution Process
+
+### 1. Issue First
+
+All contributions from outside the core team require an **Issue First** approach. Before submitting a pull request (PR), you must:
+
+- Open an issue in the repository.
+- Ensure the issue includes:
+  - **Clear problem statement:** Describe the issue or feature request.
+  - **Reproduction steps:** If reporting a bug, provide steps to reproduce it.
+  - **Proposed approach:** Outline your suggested solution or implementation.
+  - **Why this change matters:** Explain the impact or necessity of the change.
+- Tag `@sanger/psd-developers` in the issue to bring it to the attention of a maintainer.
+- Wait for the issue to be assigned or approved by a maintainer.
+
+### 2. Pull Request
+
+Once your issue is approved:
+
+- Fork the repository and create a branch for your changes.
+- Submit a PR referencing the approved issue.
+- Ensure your code adheres to the project's coding standards and passes all tests.
+
+### 3. Review
+
+Maintainers will review your PR. Address any feedback before merging.
\ No newline at end of file