Repository navigation
docs: add contributing guide and proposal template - #15
Open
chasetmartin wants to merge 1 commit into
Open
chasetmartin wants to merge 1 commit into
chasetmartin wants to merge 1 commit into
Conversation
chasetmartin
requested
a balanced review from Copilot
and removed request for
Copilot
October 30, 2026 20:59
jacob-a-brown
left a comment
jacob-a-brown
left a comment
There was a problem hiding this comment.
Just a clarifying question, otherwise I think it looks good
There was a problem hiding this comment.
Is this file the template for creating a newIssue in GitHub to propose a change? If it doesn't reside in Issues where would the proposals go?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This proposes a lightweight process for moving app customizations into the registry.
CONTRIBUTING.md: open a proposal issue, and the owners review it at sprint planning or on their own cadence. If it's accepted, it gets ported here, and a Jira ticket in the original app's backlog swaps its copy for the registry version. Also covers the porting rules (opt-in props, no app-specific code, wrap upstream components) and the sync commands..github/ISSUE_TEMPLATE/propose-customization.yml: an issue form asking for the app PR, the component and why the change helps. Blank issues still work for everything else.The template only shows up on GitHub after this merges to
main.