-
Notifications
You must be signed in to change notification settings - Fork 6
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
Use PR reviews as the voting mechanism #790
Comments
Oh hrm... but that would mean that there is still an admin class of users needed to add in the user which is something that I'd want to avoid. |
It might work if there's a way to setup an org with default of everyone as able to PR. |
I think you would want an admin to approve the changes to the voting structure. As a sec feature really. Because if you don't have that the system can be exploited. Fundamental changes like voting structures should be on a higher level than the votes on PR that touch code no? |
I always wanted to voting on the voting structure to be part of the project itself. It does suck that living within Github, we need admins still and I don't see a way around that while also being a Github Action. I think if voting to change the voting structure needs more votes than for other files, then it would be nice if it could be configured with multiple configurations. Also I think there's still flexibility for the admin add/remove voters and also circumvent rules if necessary to fix things if that's what a project wants. |
Closing as fixed. Happy to further discuss the idea of the voting structure being governed outside of git-democracy.as a new issue. |
Good idea from @dominikwilkowski that I'd like to add in here to replace the complicated comment modifications: #763 (comment)
When I started this project, I didn't consider that I actually have both 👍🏽 and 👎🏽 in a review, so no need to add another vote tallying comment to get the votes from. I think the vote summary is still useful, so I will keep that.
This does require all voters to be PR reviewers for the plugin to work. That seems acceptable for a
git-democracy
using project though.The text was updated successfully, but these errors were encountered: