Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configure GithubBot to react on certain gh issue label #10300

Open
i332322 opened this issue Apr 3, 2024 · 1 comment
Open

configure GithubBot to react on certain gh issue label #10300

i332322 opened this issue Apr 3, 2024 · 1 comment
Labels
area/ci Issues or PRs related to CI related topics

Comments

@i332322
Copy link
Contributor

i332322 commented Apr 3, 2024

Description
Is it possible to add the following configuration to the KymaBot: if a task is opened with component-requirement label, then we should get notified in the #kyma-sre channel, similarly how it is configured now with the internal-incident label and #kyma-team channel.

related conversation: https://sap-btp.slack.com/archives/CQF0V9075/p1712147440107249?thread_ts=1712141278.247829&cid=CQF0V9075

Reasons
Lately SRE has introduced a component requirement spec for all the new component that will be deployed to the control plane. component owner has to fullfil a set of criteria in order to able to go to production.
https://pages.github.tools.sap/kyma/docusaurus-docs/kyma/infra/architecture/componentreqs?_highlight=compon

Acceptance Criteria
if a new task is opened with component-requirement label, githubBot would send a message to #kyma-sre channel similarly how it sends a message to the #kyma-team channel now

Attachments
image

@i332322 i332322 added the area/ci Issues or PRs related to CI related topics label Apr 3, 2024
@i332322
Copy link
Contributor Author

i332322 commented Apr 4, 2024

Dear @TorstenD-SAP , could you please help priotize this task?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci Issues or PRs related to CI related topics
Projects
None yet
Development

No branches or pull requests

1 participant