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

[PR #2071] [MERGED] Issue 2045, Feature Request #2479

New Issue
Closed
opened 2025-12-29 03:21:27 +01:00 by adam · 0 comments
adam commented 2025-12-29 03:21:27 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/juanfont/headscale/pull/2071
Author: @dragon2611
Created: 8/22/2024
Status: ✅ Merged
Merged: 8/27/2024
Merged by: @kradalby

Base: main ← Head: main

📝 Commits (1)

  • 8107a4e Issue 2045, Feature Request

📊 Changes

1 file changed (+2 additions, -2 deletions)

View changed files

📝 .github/ISSUE_TEMPLATE/feature_request.yaml (+2 -2)

📄 Description

Requiring someone to write a design doc/contribute to the feature shouldn't be a requirement for raising a feature request as users may lack the skills required to do this.

  • have read the CONTRIBUTING.md file
  • raised a GitHub issue or discussed it on the projects chat beforehand
  • added unit tests
  • added integration tests
  • updated documentation if needed
  • updated CHANGELOG.md

Summary by CodeRabbit

  • New Features
    • Updated the feature request template to make certain fields optional, streamlining the submission process for contributors.
    • Maintained the textarea for implementation ideas, allowing users to provide input without mandatory requirements.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/juanfont/headscale/pull/2071 **Author:** [@dragon2611](https://github.com/dragon2611) **Created:** 8/22/2024 **Status:** ✅ Merged **Merged:** 8/27/2024 **Merged by:** [@kradalby](https://github.com/kradalby) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`8107a4e`](https://github.com/juanfont/headscale/commit/8107a4e154ff686e04a3efa00643c85a69d2af54) Issue 2045, Feature Request ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.github/ISSUE_TEMPLATE/feature_request.yaml` (+2 -2) </details> ### 📄 Description Requiring someone to write a design doc/contribute to the feature shouldn't be a requirement for raising a feature request as users may lack the skills required to do this. <!-- Please tick if the following things apply. You… --> - [x] have read the [CONTRIBUTING.md](./CONTRIBUTING.md) file - [x] raised a GitHub issue or discussed it on the projects chat beforehand - [ ] added unit tests - [ ] added integration tests - [x] updated documentation if needed - [ ] updated CHANGELOG.md <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Updated the feature request template to make certain fields optional, streamlining the submission process for contributors. - Maintained the textarea for implementation ideas, allowing users to provide input without mandatory requirements. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 03:21:27 +01:00
adam closed this issue 2025-12-29 03:21:27 +01:00
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 pull-request
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#2479
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?