What happens if GitHub scraper breaks (due to Instagram changes)? #3
Description
Question
What happens if GitHub scraper breaks (due to Instagram changes)?
Answer
The boilerplate ships with selector fallbacks, semantic locators, and a retry/backoff layer. When Instagram’s UI changes, failed runs capture HTML snapshots and structured error logs, making it easy to patch selectors in /scraper/selectors.* without touching business logic. CI includes smoke tests for login, feed navigation, and extraction so breaks are surfaced early. Recommended workflow: reproduce locally with saved HTML, update the locator map, add a test, and push. Use feature flags to hot-disable unstable modules while keeping the pipeline running.