-
Notifications
You must be signed in to change notification settings - Fork 8
Add initial device access options to Tailscale setup documentation #463
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add initial device access options to Tailscale setup documentation #463
Conversation
- Added "Initial Device Access Options" section with 3 clear alternatives - Documents direct SSH over same network with example - Documents physical keyboard/mouse access with use cases - Documents headless setup considerations - Addresses issue about mentioning SSH and keyboard/mouse options Co-authored-by: sgbaird <[email protected]>
Updated SSH command examples and clarified headless setup instructions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR enhances the Tailscale setup documentation by adding a dedicated section that clearly outlines different methods for accessing devices during initial setup, addressing user feedback about the need for more prominent guidance on device access options.
Key Changes
- Added a new "Initial Device Access Options" subsection with three clear alternatives for device access
- Expanded the brief SSH mention into comprehensive guidance including direct SSH, physical access, and headless setup options
- Provided practical examples and specific use cases for each access method
Co-authored-by: Copilot <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
ac-dev-lab/docs/tailscale-setup.md
Line 1 in 42f8527
# Tailscale Setup |
[P1] Commit message describes doc changes but diff is empty
This commit claims to add an “Initial Device Access Options” section and to close issue #462, but the patch contains no file modifications at all. As a result, the referenced documentation changes are not actually introduced anywhere in the repository and the linked issue remains unresolved. Please ensure the intended edits to docs/tailscale-setup.md
(or other relevant docs) are included in the commit so reviewers can verify the fix.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting
Disabled the automatic code review |
Enhances the Tailscale setup documentation by adding a dedicated section on "Initial Device Access Options" that clearly outlines different methods for accessing devices during setup.
Problem
The original documentation briefly mentioned SSH over the same WiFi network but didn't prominently discuss alternative access methods for initial device setup or troubleshooting scenarios. Users needed clearer guidance on when and how to use direct SSH access versus physical keyboard/mouse connections.
Solution
Added a new "Initial Device Access Options" subsection under General Setup Instructions that provides three clear alternatives:
Benefits
The changes are minimal and surgical, adding 18 lines of content without modifying any existing documentation or breaking the established flow.
Fixes issue requesting mention of SSH and keyboard/mouse connection options in the Tailscale setup documentation.
Original prompt
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.