Skip to content
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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ChrisChinchilla
Copy link

@ChrisChinchilla ChrisChinchilla commented Mar 12, 2025

Summary by CodeRabbit

  • Documentation
    • Updated installation instructions to guide macOS users in handling security warnings when launching the application.

Unverified

This user has not yet uploaded their public signing key.
Copy link

coderabbitai bot commented Mar 12, 2025

Walkthrough

A 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 pb binary from an unidentified developer. The note guides users to ignore the warning initially, then navigate to System Preferences > Security & Privacy to click on the Open Anyway button, and finally to click Open on the subsequent prompt.

Changes

File Change Summary
README.md Added a note in the installation section for macOS users with step-by-step instructions to handle the warning when launching the pb binary.

Poem

I'm a rabbit hopping through the code,
Skipping warnings on a comfy mac abode.
A note in the README paves the way,
So macOS users click "open" without delay.
CodeRabbit smiles with a joyful bounce today! 🐇


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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request

Copy link

@coderabbitai coderabbitai bot left a 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 Instructions

The 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.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b60e374 and 10d249b.

📒 Files selected for processing (1)
  • README.md (1 hunks)

@ChrisChinchilla
Copy link
Author

I have read the CLA Document and I hereby sign the CLA

Comment on lines +16 to +17
> 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_.

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

Copy link
Author

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

Suggested change
> 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants