From c39aafb7b5d8d3bb6852264b5d600cbb4b3533e0 Mon Sep 17 00:00:00 2001 From: Stephen Adams Date: Wed, 11 Feb 2026 11:02:23 -0500 Subject: [PATCH] Add SC Environment Impact Workflow Adding a workflow to check for impactful SC environment changes. This will drop a comment in PRs to notify the author of impactful changes and notify the rosa core team slack channel. This is non-blocking and informational to better prevent issues during release week for the security compliance environment. HCMSEC-2787 Signed-off-by: Stephen Adams --- .github/workflows/sc-environment-impact.yml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 .github/workflows/sc-environment-impact.yml diff --git a/.github/workflows/sc-environment-impact.yml b/.github/workflows/sc-environment-impact.yml new file mode 100644 index 000000000..3beaa0d79 --- /dev/null +++ b/.github/workflows/sc-environment-impact.yml @@ -0,0 +1,17 @@ +--- +# This workflow is non-blocking and runs to check PRs for changes that could impact the security compliance environment. +# #team-rosa-core will be notified so they can take a look and ensure they have the necessary changes in place in their environment before their release cycle. +name: SC Environment Check + +on: + pull_request_target: + branches: [ master ] + +jobs: + call-reusable-workflow: + permissions: + pull-requests: write + contents: read + uses: RedHatInsights/shared-workflows/.github/workflows/sc-environment-impact-check.yml@master + secrets: + SC_ASSESSOR_SLACK_URL: ${{ secrets.SC_ASSESSOR_SLACK_URL }}