kyma-project / kyma-project/manager-toolkit
Experiment #1 Turn off (Temporarily) jobs that require pull-request-target and implement notification system for failing main
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 0
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Description
As devs we don't want to manually click the "accept flow" button on every PR.
Start the experiment with one repository before spreading it to our other repositories, that repo should be keda-manager https://github.com/kyma-project/keda-manager
- We should remove everything that requires secrets from our
pulltargets and move them topushtargets. - Investigation - Check how good existing
Unit testsare and enrich them if needed - Implement a notification system that lets Otters know when one of our repository mains are failing. Whatever way you see fit. (Maybe a bot that writes to our channel "Hi Otter's job integration tests failed on Keda")
Related
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the GitHub Actions workflows for keda-manager and identify jobs on pull targets that require secrets, then review the existing unit tests. Define the notification path for failing main-branch jobs before expanding beyond that repository; done means secrets are handled on push targets, tests are adequate, and maintainers receive failure notifications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100