bagder · cooljeanius · Jan 27, 2022 · Jul 26, 2022 · Jul 15, 2023 · May 25, 2024
diff --git a/README.md b/README.md
@@ -22,13 +22,17 @@ runnning a project like [curl](https://github.com/curl/curl) easier.
 ## Issues
 
 - [Hide security issues](security-issues.md)
+- [Allow assigning groups of people (e.g. a committee, working group, etc.) as assignees for issues, rather than just individual accounts](org-assignments.md)
 
 ## Pull Requests
 
 - [Disable the merge button](disable-merge-button.md)
 - [Better support for PR-by-proxy](pr-by-proxy.md)
 - [Mark conflicting PRs in the list](mark-conflicting.md)
 - [Review commit messages](review-commit-msgs.md)
+- [Allow marking pull requests as private even in public repositories, which would then become public once merged](private-prs.md)
+- [Allow voting on whether or not to merge pull requests by people with a special "voting" permission](voting.md)
+- [More review options besides "Approve" and "Request Changes"](review-options.md)
 
 ## git integration
 

diff --git a/org-assignments.md b/org-assignments.md
@@ -0,0 +1,3 @@
+# Allow assigning groups of people (e.g. a committee, working group, etc.) as assignees for issues, rather than just individual accounts
+
+Currently, it seems that only individual accounts can be set as assignees for issues. It would be nice if issues could be assigned to organizations as well, or groups of people with a certain role within an organization, to help emulate the workflow of assigning bills to committees found in many legislatures.
diff --git a/private-prs.md b/private-prs.md
@@ -0,0 +1,3 @@
+# Allow marking pull requests as private even in public repositories (they'd become public once merged)
+
+I think GitHub might actually be working on something like this with their new private vulnerability reporting feature; we'll see what that's like once it gets out of beta...
diff --git a/review-options.md b/review-options.md
@@ -0,0 +1,3 @@
+# More review options besides "Approve" and "Request Changes"
+
+There should be a review option that's somewhere in between "Approve" and "Request changes", like "Approve pending changes" or "Don't block on this, but x, y, and z would be really nice tweaks here, and it'd be really swell if you thought so too" or something along those lines. I guess one could just say that that's what just leaving a plain comment is for, but I want the system to automatically change the review status to "Approved" for me once the changes are accepted.
diff --git a/voting.md b/voting.md
@@ -0,0 +1,3 @@
+# Allow voting on whether or not to merge pull requests by people with a special "voting" permission
+
+Some people might want to run their repositories via democracy. GitHub should help make this possible by allowing repo owners to allow voting on pull requests within it, which would then get merged (or not) depending on whether the PR reaches a certain threshold of votes among people voting on it. This could be restricted to just users with a special "voting" permission within the organization running the repository, to prevent drive-by interference and canvassing of members outside of the community.
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,3 @@
		# Allow assigning groups of people (e.g. a committee, working group, etc.) as assignees for issues, rather than just individual accounts

		Currently, it seems that only individual accounts can be set as assignees for issues. It would be nice if issues could be assigned to organizations as well, or groups of people with a certain role within an organization, to help emulate the workflow of assigning bills to committees found in many legislatures.
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,3 @@
		# Allow marking pull requests as private even in public repositories (they'd become public once merged)

		I think GitHub might actually be working on something like this with their new private vulnerability reporting feature; we'll see what that's like once it gets out of beta...
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,3 @@
		# More review options besides "Approve" and "Request Changes"

		There should be a review option that's somewhere in between "Approve" and "Request changes", like "Approve pending changes" or "Don't block on this, but x, y, and z would be really nice tweaks here, and it'd be really swell if you thought so too" or something along those lines. I guess one could just say that that's what just leaving a plain comment is for, but I want the system to automatically change the review status to "Approved" for me once the changes are accepted.
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,3 @@
		# Allow voting on whether or not to merge pull requests by people with a special "voting" permission

		Some people might want to run their repositories via democracy. GitHub should help make this possible by allowing repo owners to allow voting on pull requests within it, which would then get merged (or not) depending on whether the PR reaches a certain threshold of votes among people voting on it. This could be restricted to just users with a special "voting" permission within the organization running the repository, to prevent drive-by interference and canvassing of members outside of the community.