|
| 1 | +# Contributing |
| 2 | + |
| 3 | +The most useful thing you can send us is a broken example. |
| 4 | + |
| 5 | +## Report a bug |
| 6 | + |
| 7 | +[Open an issue](https://github.com/brightdata/amazon-scraper-python/issues) and include: |
| 8 | + |
| 9 | +- the command or the snippet you ran |
| 10 | +- what you expected, and what happened instead |
| 11 | +- your versions: `python --version` and `pip show brightdata-sdk` |
| 12 | + |
| 13 | +Paste the error text rather than a screenshot of it. Never paste your API |
| 14 | +token, in an issue or anywhere else. |
| 15 | + |
| 16 | +Questions about the API, your account or your credits go to |
| 17 | +[Bright Data support](https://brightdata.zendesk.com/hc/en-us/requests/new). |
| 18 | +We cannot see your account from here. |
| 19 | + |
| 20 | +## Send a pull request |
| 21 | + |
| 22 | +Small fixes need no permission. For anything larger, open an issue first, so |
| 23 | +that nobody writes the same code twice. |
| 24 | + |
| 25 | +Before you push, check that: |
| 26 | + |
| 27 | +- `pytest` passes offline, with no token set |
| 28 | +- `ruff check .` is clean |
| 29 | +- every fenced block in the README still runs exactly as pasted |
| 30 | + |
| 31 | +## What this repo will not take |
| 32 | + |
| 33 | +It stays small on purpose: 15 files and about 300 lines of Python. Read |
| 34 | +[AGENTS.md](AGENTS.md) first. It lists what is missing here deliberately, |
| 35 | +including retries, deduplication, scheduling, databases and concurrency. |
| 36 | + |
| 37 | +The outputs in the README come from real runs, and a scheduled job reruns them |
| 38 | +against the live API. Do not edit those blocks, the field table or the |
| 39 | +"last verified" badge by hand. |
0 commit comments