pepkit / pepkit/pepdbagent

improve efficiency of forking

Open
#129 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement wontfix
Dominant language
Python
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Forking takes a long time in big projects.
This is due to the creation of peppy object. Can we skip creation of peppy object?

Contributor guide

No contributing guide indexed for this repository

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

The issue does not name a file, test, or entry point. Start by locating the forking path and the creation of the peppy object, then measure the current behavior on a large project. Determine whether skipping that creation preserves fork behavior; done means a verified efficiency improvement with coverage for the affected behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
databases, performance
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.