-
Notifications
You must be signed in to change notification settings - Fork 129
Allow self-assignment of issues to collaborators with "pull" access #153
Comments
Is this going anywhere? It seems very odd that you can't claim an issue unless you can push. |
Maybe this could be achieved with browser extensions? Similar to https://github.com/ryanflorence/github-plusone-extension Then if I go to my Could use localStorage. Sort of like https://github.com/tessalt/echo-chamber-js |
This comment has been minimized.
This comment has been minimized.
Any movement on this? |
*rattles the cage. this would be awesome to have. any progress? |
In the Zulip project, we ended up writing a bot that effectively implements this policy through users posting comments of the form "@zulipbot claim". https://github.com/zulip/zulipbot It's a little spammy to have to do it, but is a lot better than just not being able to use issue assignment without getting everyone write access to the repository. |
I've also found this would be a great feature to have. |
why is this not a thing ? |
This comment has been minimized.
This comment has been minimized.
Add my ➕ to this feature request - as a maintainer on a project that is developed both internally and by open-source contributors, allowing our external friends to self-assign issues that they are planning to tackle would be really helpful for coordinating work across our internal ticket system and GitHub issue tracking. |
This has been open for over five years... |
Reticketed from #100
Currently, a user needs push access in order to assign as issue to themselves. This seems to put the kibosh on less trusted collaborators using the assignment feature.
It would be great if those granted "push" access could still accept responsibility for a feature, making their issue dashboard much more useful for tracking projects they submit PR's to.
Ref: geddski/grunt-release#68 (comment)
The text was updated successfully, but these errors were encountered: