PostHog / PostHog/posthog

dynamically set initial max active worktrees on users disk size

Open
#76,273 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature/desktop
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
6h 51m
Merged PRs (30d)
232

Description

e.g. if 1TB set it to 30 otherwise something more conservative like 10-15

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by locating where the initial maximum number of active worktrees is configured and where user disk size can be read; done means the initial limit adapts to disk size, including 30 for a 1TB disk and a more conservative 10–15 for smaller disks.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, python
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.