-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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 designated labels in proposals to link to related issues & pull requests #1905
Comments
We now seem to have an approach to this. A small group of community members has labeling privileges, so we can manage this. I'll go back to my proposal and put this to use now. Assuming it works nicely, I'll also submit a PR to update the proposal template. |
@tedepstein what changes to the proposals template did you have in mind? |
@MikeRalphson , this would be easier to illustrate if I could show an example, but that requires creating a new label. I can only apply labels, not create them. Could you create a new label called "Proposal: clarify-nullable" so I can show how this would work? |
@MikeRalphson , to answer your question directly, I would suggest modifying the proposal template as shown here. The proposal template would look like this. |
Looks good to me. |
@lornajane recently updated the proposals documentation -if there is still something needed here, please open an issue based on the current state of things. |
PR #1868 introduces a new workflow for proposals. As described in my comment on that PR, I think proposals should evolve through discussion in multiple related issues and pull requests.
To manage this evolution more easily I suggest we create a designated GitHub label for each draft proposal. Apply that label to relevant issues and PRs. Specify that label towards the top of the draft proposal, followed by two links:
The text was updated successfully, but these errors were encountered: