Skip to content

chore: add #python-sdk-notifications Slack channel to compass.yml [PYSDK-87]#575

Merged
helmut-hoffer-von-ankershoffen merged 1 commit into
mainfrom
chore/PYSDK-87-python-sdk-notifications-slack-channel
Apr 24, 2026
Merged

chore: add #python-sdk-notifications Slack channel to compass.yml [PYSDK-87]#575
helmut-hoffer-von-ankershoffen merged 1 commit into
mainfrom
chore/PYSDK-87-python-sdk-notifications-slack-channel

Conversation

@helmut-hoffer-von-ankershoffen

@helmut-hoffer-von-ankershoffen helmut-hoffer-von-ankershoffen commented Apr 24, 2026

Copy link
Copy Markdown
Contributor

🛡️ Implements PYSDK-87 following CC-SOP-01 Change Control, part of our ISO 13485-certified QMS | Ketryx Project

Summary

  • Adds #python-sdk-notifications (C0AUPTA5QF9) as a second CHAT_CHANNEL link in compass.yml
  • This channel is used for Jira state transition notifications via the Jira Cloud for Slack integration
  • #python-sdk-dev remains as the developer discussion channel

Why

Having a dedicated notifications channel keeps automated Jira signals (state transitions, PR status) separate from developer discussion in #python-sdk-dev, making both channels easier to follow.

Test plan

  • Merge PR
  • In #python-sdk-notifications, type /jira connect and connect the PYSDK project
  • Type /jira manage to configure: enable "Issue transitioned" notifications
  • Transition a test Jira issue and verify the notification appears in the channel

Copilot AI review requested due to automatic review settings April 24, 2026 18:00
@helmut-hoffer-von-ankershoffen helmut-hoffer-von-ankershoffen added the skip:test:long_running Skip long-running tests (≥5min) label Apr 24, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a dedicated Slack channel link for automated Jira notifications to the Atlassian Compass component definition for the Python SDK, keeping developer discussion and automated signals separated.

Changes:

  • Add #python-sdk-notifications as an additional CHAT_CHANNEL link in compass.yml.

@sonarqubecloud

Copy link
Copy Markdown

@helmut-hoffer-von-ankershoffen helmut-hoffer-von-ankershoffen marked this pull request as ready for review April 24, 2026 18:05
@helmut-hoffer-von-ankershoffen helmut-hoffer-von-ankershoffen requested a review from a team as a code owner April 24, 2026 18:05
@helmut-hoffer-von-ankershoffen helmut-hoffer-von-ankershoffen merged commit 47bbc4b into main Apr 24, 2026
29 of 31 checks passed
@helmut-hoffer-von-ankershoffen helmut-hoffer-von-ankershoffen deleted the chore/PYSDK-87-python-sdk-notifications-slack-channel branch April 24, 2026 18:06
@claude

claude Bot commented Apr 24, 2026

Copy link
Copy Markdown

Claude finished @helmut-hoffer-von-ankershoffen's task in 31s —— View job


Retrospective Review

Note: This PR is already merged

Summary

This was a simple configuration change adding the #python-sdk-notifications Slack channel to compass.yml for Atlassian Compass integration.

Observations

Appropriate change: Adding a dedicated notifications channel is good practice for separating automated Jira signals from developer discussion

Conventional commit: Follows format chore: ... with proper ticket reference [PYSDK-87]

Quality gates passed: SonarQube reported no issues

Minimal scope: Only modified compass.yml configuration - no code changes requiring tests or linting

Notes

  • This is a YAML configuration file, not Python code, so standard SDK code quality checks don't apply
  • The test plan in the PR description outlines manual verification steps for the Jira-Slack integration
  • No architectural or security concerns for this config-only change

@codecov

codecov Bot commented Apr 24, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.
see 20 files with indirect coverage changes

@helmut-hoffer-von-ankershoffen helmut-hoffer-von-ankershoffen added sop:cc-sop-01 CC-SOP-01 Change Control (feature / planned change) type:chore Tooling, maintenance, routine task (conventional chore) scope:dev-only Affects only our dev/CI env; consumers unaffected labels Apr 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

scope:dev-only Affects only our dev/CI env; consumers unaffected skip:test:long_running Skip long-running tests (≥5min) sop:cc-sop-01 CC-SOP-01 Change Control (feature / planned change) type:chore Tooling, maintenance, routine task (conventional chore)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants