Skip to content

Add process for proposals#96

Merged
mattwar merged 1 commit into
mainfrom
user/mattwar/ContributionProcess
Apr 30, 2026
Merged

Add process for proposals#96
mattwar merged 1 commit into
mainfrom
user/mattwar/ContributionProcess

Conversation

@mattwar

@mattwar mattwar commented Apr 30, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

Copilot AI review requested due to automatic review settings April 30, 2026 17:22
@mattwar mattwar merged commit b460162 into main Apr 30, 2026
5 checks passed
@mattwar mattwar deleted the user/mattwar/ContributionProcess branch April 30, 2026 17:23

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a contribution workflow that routes larger or roadmap-impacting changes through a proposal/discussion process before opening PRs.

Changes:

  • Expands CONTRIBUTING guidance to distinguish “small changes” vs “needs prior approval”.
  • Introduces a proposal-first process via GitHub Discussions, including expected proposal contents and outcomes.
  • Updates the PR checklist/process to reference the new discussion/proposal flow.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread CONTRIBUTING.md
- A rough implementation approach, if relevant
- Alternatives you considered

When you believe the discussion is ready for formal consideration, add the `design review` label. That label means a design review is requested. It does not mean the proposal has been approved.

Copilot AI Apr 30, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GitHub Discussions typically don’t support labels the same way Issues/PRs do (and contributors often can’t apply labels even where labels exist). Consider changing this to an actionable, platform-supported step (e.g., ‘comment to request design review’, ‘use a title prefix like [Design Review]’, or ‘open/convert to an issue and the team will apply the design review label’). The current instruction is likely not executable by contributors.

Suggested change
When you believe the discussion is ready for formal consideration, add the `design review` label. That label means a design review is requested. It does not mean the proposal has been approved.
When you believe the discussion is ready for formal consideration, comment on the discussion to request design review. You may also add a `[Design Review]` prefix to the discussion title to make the request clear. A design review request does not mean the proposal has been approved.

Copilot uses AI. Check for mistakes.
Comment thread CONTRIBUTING.md
- Decide to implement it internally
- Mark it as open for a community contribution

When a design is under review a corresponding issue will be opened for it that will track the proposal's progress.

Copilot AI Apr 30, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sentence is missing punctuation that clarifies the clause boundary. Consider adding a comma after ‘under review’ to improve readability (e.g., ‘When a design is under review, a corresponding issue…’).

Suggested change
When a design is under review a corresponding issue will be opened for it that will track the proposal's progress.
When a design is under review, a corresponding issue will be opened for it that will track the proposal's progress.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants