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 #2066] [MERGED] Docs: Update ACLs on file formats #2476

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/2066
Author: @Haarolean
Created: 8/21/2024
Status: ✅ Merged
Merged: 8/30/2024
Merged by: @kradalby

Base: main ← Head: patch-1

📝 Commits (1)

  • a7ef2b7 Update ACLs file format docs

📊 Changes

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

View changed files

📝 docs/acls.md (+1 -2)

📄 Description

Updated docs on ACLs according to the comment on YAML deprecation

By the way, the 'tests' link is broken and I couldn't find the files this link should mention. Any clues?

  • 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

  • Documentation
    • Updated Access Control Lists (ACLs) documentation to specify that only huJSON format is accepted, removing the previous YAML option.

🔄 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/2066 **Author:** [@Haarolean](https://github.com/Haarolean) **Created:** 8/21/2024 **Status:** ✅ Merged **Merged:** 8/30/2024 **Merged by:** [@kradalby](https://github.com/kradalby) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`a7ef2b7`](https://github.com/juanfont/headscale/commit/a7ef2b7f22cdef12d38e46dfd8876e417d523930) Update ACLs file format docs ### 📊 Changes **1 file changed** (+1 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/acls.md` (+1 -2) </details> ### 📄 Description Updated docs on ACLs according to the comment on [YAML deprecation](https://github.com/juanfont/headscale/issues/2024#issuecomment-2272976178) By the way, the 'tests' link is broken and I couldn't find the files this link should mention. Any clues? <!-- Please tick if the following things apply. You… --> - [x] have read the [CONTRIBUTING.md](./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 <!-- If applicable, please reference the issue using `Fixes #XXX` and add tests to cover your new code. --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Documentation** - Updated Access Control Lists (ACLs) documentation to specify that only huJSON format is accepted, removing the previous YAML option. <!-- 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#2476
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?