-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Install github-comment-ops
#3060
Comments
Who can use these commands? |
Anyone, they can't do anything harmful, similar to in Jira (it doesn't go quite as far though, i.e. no editing description) how anyone could update basically anything. I have created an issue to allow restricting to certain people, but I don't think required for this (happy to be persuaded): |
Limited to issues for non-members, I would hope, and not pull requests. |
Are you looking forward to enable that on the jenkinsci org? |
Yes I only implemented it for issues: |
Tested to make sure: It's not handled properly as there's a stacktrace because it still tries to close it, but it only has the code for issues |
Private repo? Got a "page not found" |
Fixed |
Presented during the last UX SIG meeting: https://www.youtube.com/watch?v=t1BSLRPNeQ4&t=2060s |
GitHub App created: https://github.com/apps/comment-ops-bot Permissions:
|
Added missing subscription to "issue comment" and "issue" events in the GitHub App settings: |
It's now working in jenkinsci organization 🎉 |
@lemeurherve did you want to raise an issue with any confusion you had or improvements? or PR the README directly? Thanks for sorting so quickly! |
I'll prepare a PR later :) Some points I'd add:
|
There is a bit of a discoverability problem here. How are users supposed to remember the list of supported commands, or find out that the whole system exists to begin with? |
I've suggested timja/github-comment-ops#36 as a first improvement.
Some suggestions:
I fear some/most won't discover this functionality, but I think the curious/frequent contributors will quickly notice these comments and what they do. |
Also, a link/quick explanation could be added as comment in the issue and pull request templates
Another (noisy) possibility: make the GitHub App comments on every new issue/PR with an "help" message. |
I plan to announce, and update the core PR template. I was planning to hold announcing till I fixed some of these issues that people have raised, but can also announce later on today if people prefer that |
Oh a question about |
Yes correct |
/label enhancement |
GitHub App installed on jenkins-infra org too 🙂 |
At Daniel's request I've temporarily limited the repositories in the jenkinsci org to:
This is to gather feedback and in a couple of weeks if there's no objections we can enable globally. There is a jenkinsci developer thread at: https://groups.google.com/g/jenkinsci-dev/c/sE7mH7hUZSY |
I've done the same on jenkins-infra organization, it's now activated only on https://github.com/jenkins-infra/helpdesk I'll open an issue to gather the use cases for jenkins-infra and the repositories needing it. |
Service(s)
Other
Summary
Hi
I've made a tool https://github.com/timja/github-comment-ops that can allow managing issues and pull requests by users without write access.
It has features like:
See the README for all features and required permissions.
It is powered by GitHub apps and is multi-tenanted so will work for any organizations that it's installed to, (i.e. only one deployment is needed).
Could we deploy this please?
I've created a helm chart for it:
https://github.com/timja/github-comment-ops/tree/main/charts/github-comment-ops
Let me know of any issues / feedback, I'd be interested in someone else doing the setup to get any feedback from something I've missed
Reproduction steps
No response
The text was updated successfully, but these errors were encountered: