| author |  Julius Marminge <julius0216@outlook.com> 2026-08-15 11:30:08+02:00 |
| committer | Julius Marminge <julius0216@outlook.com> 2026-08-15 11:30:08+02:00 |
| log | e9ae134c59bedd39428e1d279df0ada3e86cd500 |
| tree | 608f1af45663e8e767e6a7d3044555582c934d16 |
| parent | f0ebc628c6dd83fd0c7963078ad7778ce6028d0c |
docs: route feature requests to Discussions
- Disable feature-request issue templates
- Direct contributors to Ideas discussions for proposals5 files changed, 14 insertions(+), 106 deletions(-)
.github
ISSUE_TEMPLATE
- CONTRIBUTING.md
- README.md
.github/ISSUE_TEMPLATE/bug_report.yml+1
| ... | ... | @@ -9,6 +9,7 @@ body: |
| 9 | 9 | attributes: |
| 10 | 10 | value: | |
| 11 | 11 | Use this form for broken behavior, regressions, crashes, or reliability problems. |
| 12 | Feature requests belong in [Discussions](https://github.com/pingdotgg/t3code/discussions/categories/ideas). | |
| 12 | 13 | Search existing issues first and keep the report focused on one problem. |
| 13 | 14 | |
| 14 | 15 | - type: checkboxes |
.github/ISSUE_TEMPLATE/config.yml created+5
| ... | ... | @@ -0,0 +1,5 @@ |
| 1 | blank_issues_enabled: false | |
| 2 | contact_links: | |
| 3 | - name: Feature request | |
| 4 | url: https://github.com/pingdotgg/t3code/discussions/categories/ideas | |
| 5 | about: Suggest an improvement or new capability in Discussions. |
.github/ISSUE_TEMPLATE/feature_request.yml deleted-102
| ... | ... | @@ -1,102 +0,0 @@ |
| 1 | name: Feature request | |
| 2 | description: Propose a scoped improvement or new capability. | |
| 3 | title: "[Feature]: " | |
| 4 | labels: | |
| 5 | - enhancement | |
| 6 | - needs-triage | |
| 7 | body: | |
| 8 | - type: markdown | |
| 9 | attributes: | |
| 10 | value: | | |
| 11 | Use this form for new capabilities or meaningful improvements to existing behavior. | |
| 12 | This repo is still early. Small, concrete requests that clearly explain the problem and scope are much easier to evaluate. | |
| 13 | ||
| 14 | - type: checkboxes | |
| 15 | id: checks | |
| 16 | attributes: | |
| 17 | label: Before submitting | |
| 18 | options: | |
| 19 | - label: I searched existing issues and did not find a duplicate. | |
| 20 | required: true | |
| 21 | - label: I am describing a concrete problem or use case, not just a vague idea. | |
| 22 | required: true | |
| 23 | ||
| 24 | - type: dropdown | |
| 25 | id: area | |
| 26 | attributes: | |
| 27 | label: Area | |
| 28 | description: Which part of the project would this change affect? | |
| 29 | options: | |
| 30 | - apps/web | |
| 31 | - apps/server | |
| 32 | - apps/desktop | |
| 33 | - apps/mobile | |
| 34 | - packages/contracts or packages/shared | |
| 35 | - Build, CI, or release tooling | |
| 36 | - Docs | |
| 37 | - Not sure | |
| 38 | validations: | |
| 39 | required: true | |
| 40 | ||
| 41 | - type: textarea | |
| 42 | id: problem | |
| 43 | attributes: | |
| 44 | label: Problem or use case | |
| 45 | description: What are you trying to do? What is hard, slow, or impossible today? | |
| 46 | placeholder: I want to reconnect to an existing provider session after a browser refresh without losing the current thread state. | |
| 47 | validations: | |
| 48 | required: true | |
| 49 | ||
| 50 | - type: textarea | |
| 51 | id: proposal | |
| 52 | attributes: | |
| 53 | label: Proposed solution | |
| 54 | description: Describe the behavior, API, or UX you want. | |
| 55 | placeholder: Persist enough session metadata so the client can discover and reattach to the active provider session on load. | |
| 56 | validations: | |
| 57 | required: true | |
| 58 | ||
| 59 | - type: textarea | |
| 60 | id: value | |
| 61 | attributes: | |
| 62 | label: Why this matters | |
| 63 | description: Who benefits, and what outcome does this unlock? | |
| 64 | placeholder: This would make reconnects predictable during network drops and reduce accidental duplicate sessions. | |
| 65 | validations: | |
| 66 | required: true | |
| 67 | ||
| 68 | - type: textarea | |
| 69 | id: scope | |
| 70 | attributes: | |
| 71 | label: Smallest useful scope | |
| 72 | description: What is the narrowest version of this request that would still solve your problem? | |
| 73 | placeholder: A first pass only needs to support restoring the active session for the current thread. | |
| 74 | validations: | |
| 75 | required: true | |
| 76 | ||
| 77 | - type: textarea | |
| 78 | id: alternatives | |
| 79 | attributes: | |
| 80 | label: Alternatives considered | |
| 81 | description: Workarounds, prior art, or other approaches you considered. | |
| 82 | placeholder: I currently work around this by manually restarting the provider session, but that loses in-flight context. | |
| 83 | ||
| 84 | - type: textarea | |
| 85 | id: tradeoffs | |
| 86 | attributes: | |
| 87 | label: Risks or tradeoffs | |
| 88 | description: What costs, complexity, or edge cases should be considered? | |
| 89 | placeholder: This may require careful handling when the underlying provider session has already exited. | |
| 90 | ||
| 91 | - type: textarea | |
| 92 | id: references | |
| 93 | attributes: | |
| 94 | label: Examples or references | |
| 95 | description: Links, screenshots, mockups, or comparable tools. | |
| 96 | ||
| 97 | - type: checkboxes | |
| 98 | id: contribution | |
| 99 | attributes: | |
| 100 | label: Contribution | |
| 101 | options: | |
| 102 | - label: I would be open to helping implement this. |
CONTRIBUTING.md+5-3
| ... | ... | @@ -4,7 +4,9 @@ |
| 4 | 4 | |
| 5 | 5 | We are not actively accepting contributions right now. |
| 6 | 6 | |
| 7 | You can still open an issue or PR, but please do so knowing there is a high chance we close it, defer it forever, or never look at it. | |
| 7 | You can still report a bug or open a PR, but please do so knowing there is a high chance we close it, defer it forever, or never look at it. | |
| 8 | ||
| 9 | Feature requests and proposals belong in [Ideas discussions](https://github.com/pingdotgg/t3code/discussions/categories/ideas), not issues. | |
| 8 | 10 | |
| 9 | 11 | If that sounds annoying, that is because it is. This project is still early and we are trying to keep scope, quality, and direction under control. |
| 10 | 12 | |
| ... | ... | @@ -50,9 +52,9 @@ If the change depends on motion, timing, transitions, or interaction details, in |
| 50 | 52 | |
| 51 | 53 | If we have to guess what changed, we are much less likely to review it. |
| 52 | 54 | |
| 53 | ## Issues First | |
| 55 | ## Discuss Changes First | |
| 54 | 56 | |
| 55 | If you are thinking about a non-trivial change, open an issue first. | |
| 57 | If you are thinking about a non-trivial change, start a discussion first. Issues are reserved for bug reports. | |
| 56 | 58 | |
| 57 | 59 | That still does not mean we will want the PR, but it gives you a chance to avoid wasting your time. |
| 58 | 60 |
README.md+3-1
| ... | ... | @@ -113,6 +113,8 @@ Checkout their getting started guide for more information: https://viteplus.dev/ |
| 113 | 113 | vp i |
| 114 | 114 | ``` |
| 115 | 115 | |
| 116 | Read [CONTRIBUTING.md](./CONTRIBUTING.md) before opening an issue or PR. | |
| 116 | Read [CONTRIBUTING.md](./CONTRIBUTING.md) before reporting a bug or opening a PR. | |
| 117 | ||
| 118 | Have a feature request? Start an [Ideas discussion](https://github.com/pingdotgg/t3code/discussions/categories/ideas). | |
| 117 | 119 | |
| 118 | 120 | Need support? Join the [Discord](https://discord.gg/jn4EGJjrvv). |