Skip to content

Commit

Permalink
chore: GitHub workflow update (#61)
Browse files Browse the repository at this point in the history
  • Loading branch information
nepalevov authored Feb 1, 2024
1 parent 502c663 commit 0816e85
Show file tree
Hide file tree
Showing 9 changed files with 36 additions and 22 deletions.
2 changes: 2 additions & 0 deletions .github/CODEOWNERS
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
* @vladisavvv
/.github/ @nepalevov @alexey-ban
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
blank_issues_enabled: false
14 changes: 0 additions & 14 deletions .github/pr-title-checker-config.json

This file was deleted.

8 changes: 4 additions & 4 deletions .github/workflows/deploy_dev.yml
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,11 @@ 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.1.0
uses: epam/ai-dial-ci/.github/workflows/deploy-development.yml@1.3.1
with:
gitlab-project-id: '1824'
gitlab-project-ref: 'master'
gitlab-project-id: "1824"
gitlab-project-ref: "master"
secrets:
DEPLOY_HOST: ${{ secrets.DEPLOY_HOST }}
DEPLOY_ACCESS_TOKEN: ${{ secrets.DEPLOY_ACCESS_TOKEN }}
DEPLOY_TRIGGER_TOKEN: ${{ secrets.DEPLOY_TRIGGER_TOKEN }}
DEPLOY_TRIGGER_TOKEN: ${{ secrets.DEPLOY_TRIGGER_TOKEN }}
2 changes: 1 addition & 1 deletion .github/workflows/e2e_tests.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ on:
jobs:
e2e-tests:
if: ${{ github.event.registry_package.package_version.container_metadata.tag.name == 'development' }}
uses: epam/ai-dial-ci/.github/workflows/e2e-test.yml@1.1.0
uses: epam/ai-dial-ci/.github/workflows/e2e-test.yml@1.3.1
with:
gitlab-project-id: "1843"
secrets:
Expand Down
14 changes: 14 additions & 0 deletions .github/workflows/pr-title-check.yml
Original file line number Diff line number Diff line change
@@ -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/[email protected]
secrets:
ACTIONS_BOT_TOKEN: ${{ secrets.ACTIONS_BOT_TOKEN }}
2 changes: 1 addition & 1 deletion .github/workflows/pr_check_tests.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ on:

jobs:
run_tests:
uses: epam/ai-dial-ci/.github/workflows/test_python_docker.yml@1.1.0
uses: epam/ai-dial-ci/.github/workflows/test_python_docker.yml@1.3.1
with:
bypass_checks: false
python_version: 3.11
Expand Down
4 changes: 2 additions & 2 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,12 +2,12 @@ name: Release version

on:
push:
branches: [ development, release-* ]
branches: [development, release-*]

env:
IMAGE_NAME: ${{ github.repository }}

jobs:
release:
uses: epam/ai-dial-ci/.github/workflows/publish_python_docker.yml@1.1.0
uses: epam/ai-dial-ci/.github/workflows/publish_python_docker.yml@1.3.1
secrets: inherit
11 changes: 11 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -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-adapter-openai/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.

0 comments on commit 0816e85

Please sign in to comment.