From 896203868fe1310fe2095c06feca6d8770b630c2 Mon Sep 17 00:00:00 2001
From: Sebastian Opriel <22075788+SebastianOpriel@users.noreply.github.com>
Date: Wed, 30 Oct 2024 09:17:33 +0100
Subject: [PATCH 1/2] Update epic_template.md (#1072)

Co-authored-by: Eric Fiege <105237007+efiege@users.noreply.github.com>
---
 .github/ISSUE_TEMPLATE/epic_template.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/.github/ISSUE_TEMPLATE/epic_template.md b/.github/ISSUE_TEMPLATE/epic_template.md
index 24edb0b59..390a48995 100644
--- a/.github/ISSUE_TEMPLATE/epic_template.md
+++ b/.github/ISSUE_TEMPLATE/epic_template.md
@@ -13,6 +13,7 @@ assignees: ""
 
 ### Requirements
 <!-- Which requirements do you have to be fulfilled? -->
+<!-- Which security-related requirements must be satisfied? -->
 
 ## Work Breakdown
 <!-- If you already know what needs to be done, plase add a tasklist. -->
@@ -22,6 +23,10 @@ assignees: ""
 - [ ] Create Stories which can be converted into issues
 ```
 
+### Security Constraints
+<!-- Which constraints can be checked that must be covered by the work breakdown? -->
+- [ ] Final solution design has been challenged for security related topics
+
 ## Initiative / goal
 <!-- Describe how this Epic impacts an initiative the business is working on. -->
 
@@ -29,7 +34,7 @@ assignees: ""
 <!-- What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit. -->
 
 ## Acceptance criteria and must have scope
-<!-- Define what is a must-have for launch and in-scope. Keep this section fluid and dynamic until you lock-in priority during planning. Please list your criteria below. -->
+<!-- Define what is a must-have for launch and in-scope (e.g. security-related tasks like successful pen-tests). Keep this section fluid and dynamic until you lock-in priority during planning. Please list your criteria below. -->
 
 ## Stakeholders
 <!-- Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the epic project. -->

From fd8a8703e530fc16250d866d8db1d003e3cd966f Mon Sep 17 00:00:00 2001
From: sovitybot <107936402+sovitybot@users.noreply.github.com>
Date: Wed, 30 Oct 2024 09:20:03 +0100
Subject: [PATCH 2/2] =?UTF-8?q?=F0=9F=94=84=20Templates:=20synced=20file(s?=
 =?UTF-8?q?)=20with=20sovity/PMO-Software=20(#1071)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* 🔄 Templates: synced local '.github/PULL_REQUEST_TEMPLATE.md' with remote '.github/PULL_REQUEST_TEMPLATE.md'

* 🔄 Templates: synced local '.github/ISSUE_TEMPLATE/epic_template.md' with remote '.github/ISSUE_TEMPLATE/epic_template.md'

* 🔄 Templates: synced local '.github/ISSUE_TEMPLATE/feature_request.md' with remote '.github/ISSUE_TEMPLATE/feature_request.md'

* 🔄 Templates: synced local '.github/workflows/add_issue_to_project.yml' with remote '.github/workflows/add_issue_to_project.yml'

* Update PULL_REQUEST_TEMPLATE.md

---------

Co-authored-by: sovitybot <null>
Co-authored-by: Sebastian Opriel <22075788+SebastianOpriel@users.noreply.github.com>
---
 .github/workflows/add_issue_to_project.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/add_issue_to_project.yml b/.github/workflows/add_issue_to_project.yml
index aa1b8c7bc..655427ddb 100644
--- a/.github/workflows/add_issue_to_project.yml
+++ b/.github/workflows/add_issue_to_project.yml
@@ -11,7 +11,7 @@ jobs:
     name: add_issue_to_project
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/add-to-project@v1.0.1
+      - uses: actions/add-to-project@v1.0.2
         with:
           project-url: https://github.com/orgs/sovity/projects/9
           github-token: ${{ secrets.ADD_ISSUE_TO_PROJECT_PAT }}