-
-
Notifications
You must be signed in to change notification settings - Fork 10
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 macos security warning #82
base: main
Are you sure you want to change the base?
Conversation
WalkthroughA new note has been added to the installation section of the README file for macOS users. This note provides specific instructions on how to bypass a warning generated when opening the Changes
Poem
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
CLA Assistant Lite bot: I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request |
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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
README.md (1)
15-16
: Clear and Helpful macOS Security InstructionsThe added note for macOS users is clear and provides step-by-step instructions on how to bypass the security warning when launching the
pb
binary. This should effectively guide users unfamiliar with macOS's security prompts. Consider verifying the consistency of styling for callouts (e.g., using[NOTE]
) across your documentation if applicable.
I have read the CLA Document and I hereby sign the CLA |
> If you receive a warning on macOS about the binary being from an unidentified developer, ignore the warning, then open _System Preferences_ > _Security & Privacy_, and click the new _Open Anyway_ message that shows for pb. Then the second time you launch pb, macOS shows a dialog asking if you want to open the application. Click _Open_. | ||
|
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.
An easier way to do this would be to simply run the below command in terminal:
xattr -d com.apple.quarantine path/to/pb
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.
Sure thing, how about this @garg3133
> If you receive a warning on macOS about the binary being from an unidentified developer, ignore the warning, then open _System Preferences_ > _Security & Privacy_, and click the new _Open Anyway_ message that shows for pb. Then the second time you launch pb, macOS shows a dialog asking if you want to open the application. Click _Open_. | |
> If you receive a warning on macOS about the binary being from an unidentified developer, run: | |
```bash | |
xattr -d com.apple.quarantine path/to/pb |
Summary by CodeRabbit