Repository navigation
docs: recommend the udev rule wherever Wayland clicks are mentioned - #1102
Merged
Merged
Conversation
The install page now recommends a udev uaccess rule for pointer devices and keeps the input group as a fallback. README, the native README, Recording, the product demo guide and the Linux, auto-zoom and Loom pages still said the group was required; they now name both and link to the install section.
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to The documentation adds a narrower udev setup alongside the broader input-group option. No material merge risk is evident. Pre-merge checks |
 |
| Check name | Status | Explanation |
|---|---|---|
| Title check |  |
The title clearly identifies the main documentation change: recommending a udev rule wherever Wayland click guidance appears. |
| Description check | |
The description follows the repository template and includes the summary, related issue, change type, release impact, platform impact, screenshots note, and testing details. |
| Docstring Coverage | |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
✨ Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The install page recommends a udev
uaccessrule for pointer devices and keeps theinputgroup as a fallback. Every other page still said the group was required. They now name both, udev first, and link to the install section instead of copying the rule.README.md,electron/native/README.md, Recording, the product demo guide, and the Linux, auto-zoom and Loom pages.Related issue
Refs #1099
Type of change
Release impact
Desktop impact
Screenshots / video
N/A, text only.
Testing
npm run docs:checkpasses.git grepshows no page outside the install page that names theinputgroup without the udev rule.🤖 Generated with Claude Code
Summary by CodeRabbit
inputgroup membership.inputgroup provides broader access to input devices.