Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement]: Using GPT Pilot for existing projects #381

Open
saleh-mir opened this issue Dec 21, 2023 · 11 comments
Open

[Enhancement]: Using GPT Pilot for existing projects #381

saleh-mir opened this issue Dec 21, 2023 · 11 comments
Labels
enhancement New feature or request

Comments

@saleh-mir
Copy link

Congratulation on the amazing project. It is exactly what I've been thinking project generation should be.

Is it possible to use GPT-Pilot inside a project that already has a certain amount of code in it?

Preferably, is it possible for GPT-Pilot to make the other code similar to the existing code? For example, in a web application, if I have implemented a certain number of endpoints, I need GPT-Pilot to implement the remaining functionalities similar to the previous ones.

@roscoevanderboom
Copy link

I second this feature request. It would be great to have "Create New Project" or "Import Existing Project". By pointing GPT-Pilot to a package.json file, it could understand the project details. When scanning, it could ignore certain folders like "/node_modules" to save time.

@evgenyfadeev
Copy link

evgenyfadeev commented Dec 24, 2023

or allow cloning a git repo into the project, indexing it, learning of the technologies used and taking from there. Probably you will want to fill in the information about the features, point to the implementation of each feature and the corresponding test cases... Could be quite a bit of work to get started with a large project.

Have you considered bootstrapping this project with gpt-pilot?

@svallory
Copy link

I believe this should be handled by using aider

They are focused on understanding existing codebases and trying to solve that issue for large ones

In fact, maybe a merger or deeper collaboration between both projects could generate a de facto standard for coding agents

@outrank-james
Copy link

Great suggestion - would love something like this to be able to handle projects that have been going on for many years - would streamline a lot of work going forward on projects that already exist.

@cranyy
Copy link

cranyy commented Mar 10, 2024

any updates on this?

@techjeylabs techjeylabs changed the title Using GPT Pilot for existing projects [Enhancement]: Using GPT Pilot for existing projects Apr 24, 2024
@techjeylabs techjeylabs added the enhancement New feature or request label Apr 24, 2024
@techjeylabs techjeylabs pinned this issue Apr 24, 2024
@zkewind
Copy link

zkewind commented May 7, 2024

Is anyone implementing this feature?

@IncomeStreamSurfer
Copy link

please god implement this feature PLEAAAAAAAAAAAAAAAAAAASE

@IncomeStreamSurfer
Copy link

i feel literally stuck on a massive project i am working on because the bot considers it finished and won't let me work on it, and i have now changed the code myself beyond its recognition. it's proving super hard to do anything. I'd love to just be able to open my code as it is currently working and then run gpt pilot. Just add a .gptpilot.ignore or whatever for all the node modules etc... plsplsplslsp do this

@5eqn
Copy link

5eqn commented May 21, 2024

Some ideas about implementing this feature:

Based on my current understanding of the codebase, the following fields are required to form a valid project:

  • name (just simply ask user)
  • project description (just simply ask user)
  • user stories (can be inferred from project description, add a confirm step for this?)
  • architecture (just simply ask user)
  • dependencies (extract from package.json?)
  • previous features (filter implemented features from project tasks)
  • future features (sort unimplemented features reasonably?)

If these can be generated, we can theoretically integrate on existing project.

How does it look?

@IncomeStreamSurfer
Copy link

Some ideas about implementing this feature:

Based on my current understanding of the codebase, the following fields are required to form a valid project:

  • name (just simply ask user)
  • project description (just simply ask user)
  • user stories (can be inferred from project description, add a confirm step for this?)
  • architecture (just simply ask user)
  • dependencies (extract from package.json?)
  • previous features (filter implemented features from project tasks)
  • future features (sort unimplemented features reasonably?)

If these can be generated, we can theoretically integrate on existing project.

How does it look?

Whatever you need to do do it - thank you

@zkewind
Copy link

zkewind commented May 24, 2024

It's done. See PR #952.

Since it may take a long time for the review and release of the new version of the program, you can manually copy the two files from the PR to the project source code directory for use. Refer to the header of ./pilot/load_exist.py for usage instructions. The other file is pilot/prompts/documentation/summary_codebase.prompt.

Please note that due to the context limitations of large language models (LLMs) and the implementation of the program, there is a limit on the number of source code files that can be loaded. This depends on the token limit of the LLM and the size of the source files. It is recommended to use an LLM API that supports a larger context token count if possible. You can experiment with the Example_Project that comes with the gpt-pilot project.

Or ,https://github.com/zkewind/gpt-pilot-cn/tree/load_exits_project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

10 participants