No need to propagate skip_local through
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 10
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 4
Description
You can do all the local logic lookup above this
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read src/choreographer/browsers/chromium.py around line 84, then trace where skip_local is passed into this logic. Confirm the local lookup is handled before that point and identify the relevant tests or test suite to run; done means skip_local is no longer propagated while the existing browser behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100