You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: Add ACTIONS_BOT_TOKEN and VBOT_GITHUB_API_TOKEN to token check (#167)
* fix: Add ACTIONS_BOT_TOKEN and VBOT_GITHUB_API_TOKEN to token check
The getGitHubToken() helper was missing ACTIONS_BOT_TOKEN (used in CI) and
VBOT_GITHUB_API_TOKEN (used in legacy code), causing authentication to fail
and hitting unauthenticated rate limits (60 req/hr instead of 5000 req/hr).
This was causing 403/429 errors when checking cloud-docs for 471 connectors.
Updated token priority order:
1. REDPANDA_GITHUB_TOKEN
2. ACTIONS_BOT_TOKEN (CI)
3. GITHUB_TOKEN (GitHub Actions default)
4. VBOT_GITHUB_API_TOKEN (legacy)
5. GH_TOKEN (GitHub CLI)
* chore: Bump version to 4.13.6
* perf: Optimize cloud-docs checking from 471 API calls to 1
Use GitHub Tree API to fetch entire directory structure in a single API call
instead of checking each connector individually. This reduces API calls from
471 to 1, making the check ~108x faster (from 30-60s to ~280ms).
Changes:
- Fetch recursive tree of modules/develop/pages/connect/components/
- Build in-memory set of existing files for O(1) lookup
- Check connectors against this set (no additional API calls)
- Graceful fallback to individual checks if tree API fails
Performance:
- OLD: 471 individual API calls (~30-60 seconds)
- NEW: 1 tree API call (~280ms)
- Speedup: 108x faster
* refactor: Remove emojis from cloud-docs checking output
Replace emoji characters with standard text labels (INFO, WARNING) for
better compatibility and cleaner log output.
0 commit comments