chore: GitHub workflow update (#18)

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+* @astsiapanay
+/.github/ @nepalevov @alexey-ban

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/workflows/deploy_dev.yml

@@ -6,7 +6,7 @@ on:
 jobs:
   gitlab-dev-deploy:
     if: ${{ github.event.registry_package.package_version.container_metadata.tag.name == 'development' }}
-    uses: epam/ai-dial-ci/.github/workflows/deploy-development.yml@1.0.1
+    uses: epam/ai-dial-ci/.github/workflows/deploy-development.yml@1.3.1
     with:
       gitlab-project-id: '1831'
       gitlab-project-ref: 'master'

.github/workflows/pr-title-check.yml

@@ -0,0 +1,14 @@
+name: "Validate PR title"
+
+on:
+  pull_request_target:
+    types:
+      - opened
+      - edited
+      - synchronize
+
+jobs:
+  pr-title-check:
+    uses: epam/ai-dial-ci/.github/workflows/pr-title-check.yml@1.3.1
+    secrets:
+      ACTIONS_BOT_TOKEN: ${{ secrets.ACTIONS_BOT_TOKEN }}

.github/workflows/pr_check_tests.yml

@@ -8,7 +8,7 @@ on:
 
 jobs:
   run_tests:
-    uses: epam/ai-dial-ci/.github/workflows/test_gradle_docker.yml@1.0.2
+    uses: epam/ai-dial-ci/.github/workflows/test_gradle_docker.yml@1.3.1
     secrets: inherit
     with:
       bypass_checks: false

.github/workflows/release.yml

@@ -9,5 +9,5 @@ env:
 
 jobs:
   release:
-    uses: epam/ai-dial-ci/.github/workflows/publish_gradle_docker.yml@1.0.2
+    uses: epam/ai-dial-ci/.github/workflows/publish_gradle_docker.yml@1.3.1
     secrets: inherit

SECURITY.md

@@ -0,0 +1,11 @@
+# Reporting Security Issues
+
+We take all security reports seriously. We appreciate your efforts to responsibly disclose your findings and will make every effort to acknowledge your contributions.
+
+⚠️ Please do *not* file GitHub issues for security vulnerabilities as they are public! ⚠️
+
+To report a security issue, please use the GitHub Security Advisory ["Report a Vulnerability"](https://github.com/epam/ai-dial-auth-helper/security/advisories/new) tab. Tip: In this form, only the title and description are mandatory.
+
+We will send a response indicating the next steps in handling your report. After the initial reply to your report, we will keep you informed of the progress toward a fix and full announcement and may ask for additional information or guidance.
+
+When we receive such reports, we will investigate and subsequently address any potential vulnerabilities as quickly as possible.