Repository navigation
Conversation
Export BROWSERSTACK_USERNAME / BROWSERSTACK_ACCESS_KEY in the shell and never commit them; the CLI reads them from the environment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@coderabbitai review |
Action performed
|
Hidden prompt for the access key so it stays out of bash/zsh and PSReadLine history (CodeRabbit); note the variables last for the current session and how to spot an unset one; per-repo fixes from the code review. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@coderabbitai review |
Action not completed
|
|
@coderabbitai review |
Action not completed
|
Prompt and export on one line, so pasting the block can't feed the export line to read. Robot: per-OS signature check, .gitignore for the CLI binary. Selenium: ignore browserstack-cli.exe. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
zsh (macOS default) has interactive_comments off, so pasted '#' lines printed errors; the labels now sit outside the sh fences. The placement note names browserstack-cli.exe for Windows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@coderabbitai review |
Action performed
|
codesign -dv's TeamIdentifier can be forged on an ad hoc signature; require an Apple-anchored leaf cert with OU YQ5FZQ855D instead (checked against the current macOS arm64 build: passes; a wrong OU fails). Add chmod +x after unzip (CodeRabbit). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@coderabbitai review |
Action performed
|
Adds a Set your credentials step to the README. It covers exporting
BROWSERSTACK_USERNAME/BROWSERSTACK_ACCESS_KEYin the shell (macOS/Linux and PowerShell) and never committing them. The CLI reads both from the environment.Asked for in BrowserStack Security's retest of LTS-5452: the sample READMEs had no step for setting credentials.
JIRA: https://browserstack.atlassian.net/browse/LTS-5452
🤖 Generated with Claude Code
Summary by CodeRabbit