Auto-assign issues #73
Conversation
Close with merging will close the issues (by definition), so in that case there is no need to unassign.
|
This basically works the way I want it to. I just need to add tests and update the existing tests. But it would be good to get a concept review first to see if this is something we actually want to do. |
|
OK, here's a snag. It looks like you can't actually assign people to an issue unless they are members of the organization. I know GitHub has had requests to change this, but it hasn't happened yet. So we either need to sit on this until they do, or implement #68 (give all PR authors Triage permissions). #68 would have other advantages as well, and I think it wouldn't be too hard. One issue is that if a user is given Triage permissions, I don't know if you can assign them to issues right away or if they have to accept the invite first. If they have to accept the invite, then the bot wouldn't be able to assign them until some future PR event that occurs after they accept the invite (we could enable comment webhook updates if this is the case to get more pushes; we should still be fine for being under API limits I'd imagine). |
|
I guess you can assign anyone who has commented on the issue. That should cover most of the use cases. We can post a comment asking people to comment on the issue about the pull request if they haven't commented on the issue. |
|
GitHub now has a way to link issues without using "Fixes" but I don't see anything about it in the API. |
|
Might wait to see if they add it. It would make the logic here a lot simpler. |
Fixes #72
Still a work in progress but the basic concept works. See asmeurer/GitHub-Issues-Test#43