Start cloning as soon as possible in bot tasks
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 67
- Forks
- 52
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 54
Description
We are currently doing a few things before starting to clone the repo, which starts around 20 seconds in the task.
We could start cloning earlier in the background while we do other stuff, so we save the 20 seconds (assuming what we're doing is not I/O bound and mostly waiting for other services to respond).
Contributor guide
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
Trace the bot task setup to find where repository cloning is invoked and what work currently happens before it. Review the task's ordering and interactions with other services, then verify that cloning starts earlier without disrupting those steps and that the roughly 20-second wait is reduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100