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.

Sign up for GitHub

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

Jump to bottom

Decide what to do with fails #87

Open

discombobulateme opened this issue Jan 19, 2021 · 0 comments

Projects

3.0 enhacements

Collaborator

discombobulateme commented Jan 19, 2021 •

edited

Loading

In current set up we are just seeing the results. What happens and how to take action to solve what is failing?

Automated possible solutions:

[] Send email to code owner making them aware of the issue. Problem: as it is linted daily, the tool may spam the code owner until issue is fixed
[] Create a PR with model/ template to fix what is failing. Problem: same as with email, it may create several PRs until issue is solved

Manual solution:

[] Directly talking to code owners or teams or project managers. Although overwhelming, this can be an opportunity to create networks between OSPO and other teams

Still a problem when repository has no code owners

discombobulateme created this issue from a note in 3.0 enhacements (To do)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment