Conversation
- Align with docenv.example format - Show API tokens as recommended method (Option 1) - Move app password to legacy section (Option 2) - Add deprecation warnings matching other documentation - Add BB_TEST_COUNTER as optional setting Closes gap where env_setup.sh.example was not updated in v1.2.7 when API token support was added.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 85f24d2af7
ℹ️ 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 "@codex address that feedback".
| export BB_EMAIL=your.email@example.com | ||
| export BB_API_TOKEN=ATBBxxx... |
There was a problem hiding this comment.
For users who still need the legacy app-password flow before June 9, 2026, this template is now misleading: bb-ripper/auth_helper.py:get_auth_mode() switches to API-token auth whenever BB_API_TOKEN exists, regardless of whether BB_USER/BB_PASSWORD are also set. Because this file exports BB_API_TOKEN unconditionally, someone who follows the “Choose ONE” instructions and only uncomments Option 2 will still be forced down the token path and get auth failures until they realize they must also re-comment Option 1.
Useful? React with 👍 / 👎.
1 participant
Changes
Updates
env_setup.sh.exampleto align with the API token migration strategy introduced in v1.2.7.What changed
docenv.exampleformatBB_TEST_COUNTERas an optional settingWhy
In v1.2.7, API token support was added and
docenv.examplewas updated, butenv_setup.sh.examplestill only showed app password variables. This closes that gap.Related
docenv.example