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

[PR #324] [MERGED] Update README.md #1384

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

📋 Pull Request Information

Original PR: https://github.com/juanfont/headscale/pull/324
Author: @m-tanner-dev0
Created: 2/18/2022
Status: ✅ Merged
Merged: 2/18/2022
Merged by: @kradalby

Base: main ← Head: patch-1

📝 Commits (1)

📊 Changes

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

View changed files

📝 README.md (+2 -2)

📄 Description

I would like to convince my teammates at my company to use headscale, but they were immediately turned off by some of the casual language in the README. I have proposed a couple small changes so that this doesn't happen. I'm really excited to work with Headscale and I'm hoping I can help my colleagues feel the same way!

  • read the CONTRIBUTING guidelines
  • 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

🔄 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/324 **Author:** [@m-tanner-dev0](https://github.com/m-tanner-dev0) **Created:** 2/18/2022 **Status:** ✅ Merged **Merged:** 2/18/2022 **Merged by:** [@kradalby](https://github.com/kradalby) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`61bfa79`](https://github.com/juanfont/headscale/commit/61bfa79be2313e7458a7379b5dd6d1836356f20e) Update README.md ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+2 -2) </details> ### 📄 Description I would like to convince my teammates at my company to use headscale, but they were immediately turned off by some of the casual language in the README. I have proposed a couple small changes so that this doesn't happen. I'm really excited to work with Headscale and I'm hoping I can help my colleagues feel the same way! <!-- Please tick if the following things apply. You… --> - [x] read the [CONTRIBUTING guidelines](README.md#user-content-contributing) - [ ] 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 <!-- If applicable, please reference the issue using `Fixes #XXX` and add tests to cover your new code. --> --- <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 02:29:53 +01:00
adam closed this issue 2025-12-29 02:29:53 +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#1384
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?