-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
[prometheus-snmp-exporter] Extra maintainers #4158
Comments
@prometheus-community/helm-charts-admins apologies for the direct mention but are you able to help with this at all as mentioned in https://github.com/prometheus-community/helm-charts/blob/main/PROCESSES.md#review-process? Thanks in advance. |
@walker-tom Absolutely! I have little time for it at the moment so having more people to help would be great! Can you create a PR adding yourself as a maintainer to the chart? |
I've invited @walker-tom to the @prometheus-community/helm-charts-maintainers team. |
(Lock/unlock was a missclick, sorry) |
Nice to see a maintainer on this, welcome @walker-tom hint hint nudge nudge #4086 😆 |
Describe the bug a clear and concise description of what the bug is.
Hello,
The
prometheus-snmp-exporter
chart is a few versions behind prometheus/snmp_exporter and there are multiple open PRs to update it that haven't been reviewed:The maintainers are down as @Miouge1 and @xiu according to CODEOWNERS but there are errors for @Miouge1 (suggesting they may not have write access), so it is just @xiu that gets added to PRs.
Are the maintainers open in having any additional maintainers help out? I would be happy to volunteer if so. Thanks!
What's your helm version?
N/A
What's your kubectl version?
N/A
Which chart?
prometheus-snmp-exporter
What's the chart version?
N/A
What happened?
No response
What you expected to happen?
No response
How to reproduce it?
No response
Enter the changed values of values.yaml?
No response
Enter the command that you execute and failing/misfunctioning.
N/A
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: