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
Add issue triage workflow #2142
Add issue triage workflow #2142
Conversation
89ddceb
to
0f6656d
Compare
@arminru @Aneurysm9 @tedsuo you voted for the issue, please review the PR :-) |
@open-telemetry/specs-approvers we need more eyes on this. |
@tigrannajaryan Technically we have enough reviews. I'd suggest we mention this in the Spec meeting next week, and merge afterwards. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you Tigran!
Resolves open-telemetry#1962 I also looked at Kubernetes triage workflow: https://github.com/kubernetes/community/blob/master/contributors/guide/issue-triage.md I ended up not using it because it is significantly more complicated and requires a usage of tools. However, we may still decide to replicate what Kubernetes does if this propsal proves to be inefficient.
48d74ab
to
b128dd6
Compare
@lucaspimentel please review, this affects all approvers. |
Hmm, autocomplete is strange. I meant to write: @open-telemetry/specs-approvers please review, this affects all approvers. |
Resolves #1962
I also looked at Kubernetes triage workflow:
https://github.com/kubernetes/community/blob/master/contributors/guide/issue-triage.md
I ended up not using it because it is significantly more complicated
and requires a usage of tools. However, we may still decide to replicate
what Kubernetes does if this propsal proves to be inefficient.