starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[Bug] Feature request form #759

New Issue
Closed
opened 2025-12-29 02:23:29 +01:00 by adam · 2 comments
adam commented 2025-12-29 02:23:29 +01:00
Owner
Copy Link

Originally created by @dragon2611 on GitHub (Aug 5, 2024).

Is this a support request?

  • This is not a support request

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

The feature request form will only let you proceed if you are wiling to state you can write a design doc/contribute to a feature.

This feels like a bug as whilst anyone requesting a feature should participate in the discussion and help where they can, not everyone has the technical expertise to work on producing a design doc/implement the feature themselves.

image

Expected Behavior

I think these tickboxes probably weren't meant to be mandatory?

Steps To Reproduce

raise a feature request on github

Environment

N/A - Github issue

Runtime environment

  • Headscale is behind a (reverse) proxy
  • Headscale runs in a container

Anything else?

No response

Originally created by @dragon2611 on GitHub (Aug 5, 2024). ### Is this a support request? - [X] This is not a support request ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior The feature request form will only let you proceed if you are wiling to state you can write a design doc/contribute to a feature. This feels like a bug as whilst anyone requesting a feature should participate in the discussion and help where they can, not everyone has the technical expertise to work on producing a design doc/implement the feature themselves. ![image](https://github.com/user-attachments/assets/cd46fbc2-e67f-4631-87e3-c6bdbe9e0e84) ### Expected Behavior I think these tickboxes probably weren't meant to be mandatory? ### Steps To Reproduce raise a feature request on github ### Environment ```markdown N/A - Github issue ``` ### Runtime environment - [ ] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Anything else? _No response_
adam added the bug label 2025-12-29 02:23:29 +01:00
adam closed this issue 2025-12-29 02:23:29 +01:00
adam commented 2025-12-29 02:23:29 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Aug 11, 2024):

Yes it does sound like an oversight, would be great to get a PR to rectify it.

@kradalby commented on GitHub (Aug 11, 2024): Yes it does sound like an oversight, would be great to get a PR to rectify it.
adam commented 2025-12-29 02:23:30 +01:00
Author
Owner
Copy Link

@dragon2611 commented on GitHub (Aug 22, 2024):

PR raised, https://github.com/juanfont/headscale/pull/2071

@dragon2611 commented on GitHub (Aug 22, 2024): PR raised, https://github.com/juanfont/headscale/pull/2071
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#759
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?