Files
zed/.github/DISCUSSION_TEMPLATE/feature-requests.yml
Mohamad Khani b9819977a5 logiguard fork v3: full patch set on verified 8c74db0 tree
Includes prior-session patches (carry forward so the app compiles):
  - crates/gpui/build.rs: cross-compile manifest fix
  - crates/gpui/src/platform.rs: PlatformWindow::activate_with_token trait method
  - crates/gpui/src/window.rs: Window::activate_with_token public API
  - crates/gpui_linux/src/linux/wayland/window.rs: WaylandWindow::activate_with_token + activate() keyboard-serial fix

Plus the focus-serial fix:
  - serial.rs: SerialKind::KeyboardEnter
  - client.rs: store wl_keyboard.enter serial; latest_serial_of()

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-14 01:52:12 +03:30

44 lines
1.0 KiB
YAML

body:
- type: markdown
attributes:
value: |
# Feature Request
Welcome! 👋
If you are interested in proposing a new feature, improvement, or change to Zed, you are in the right place.
Use this template to suggest a new feature, improvement, or change.
- type: textarea
id: main
attributes:
label: Body
value: |
# What are you proposing?
Describe the feature, improvement, or change at a high level.
# Why does this matter?
What problem does this solve?
What becomes easier or possible?
# Are there any examples or context?
Screenshots, mockups, workflows, or examples from other tools.
# Possible approach
If you have ideas about how this could work, share them here.
validations:
required: true
- type: markdown
attributes:
value: |
Learn more about how feature requests work in our
[Feature Request Guidelines](https://github.com/zed-industries/zed/discussions/51422).