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

Roadmap #1

Open
alexeykudinkin opened this issue Jul 9, 2015 · 3 comments
Open

Roadmap #1

alexeykudinkin opened this issue Jul 9, 2015 · 3 comments
Milestone

Comments

@alexeykudinkin
Copy link
Collaborator

Let's this be a meta-issue.

@alexeykudinkin
Copy link
Collaborator Author

Don't hesitate to push here the stuff you're want to see working up to Saturday morning.

@alexeykudinkin
Copy link
Collaborator Author

Some cases that would be nice to see:

  • Ok, Google, what is a HashMap (or whatever)?
    • Some fancy response like ("Ok, Alexey, you're supposed to know what a HashMap is") would be super-cool
  • Go to the assignment of the field 'X'
    • Here we'd need to maintain context (that we're inside some method of class that has field named 'X', etc., that'd Yaroslav shining moment)

@alexeykudinkin alexeykudinkin added this to the v0.1 milestone Jul 9, 2015
@nalbion
Copy link
Member

nalbion commented Apr 24, 2023

I've created a branch for integration with OpenAI.

The gpt-developer GitHub action provides an example of a prompt which can be used to programmatically interact with an LLM:

Commands:
read: Read files
    read <comma separated filenames>
write: Write contents to a file a file
    write <filename> <<EOF
    <contents>
    EOF
remove: Remove files
    remove <comma separated filenames>
commit: Set the commit message
    commit <message>
comment: Set the comment message
    comment <<EOF
    <message>
    EOF
exit: Exit the program
    exit

Existing files: {files}
You are interacting with software. Solve the issue detailed above using the commands documented above. You use commands to `read`, `write`, `remove` files in the code and then `comment` on the issue or `commit` the changes. `exit` to stop.
You need to use the commands. The text you write is being parsed by a custom software that executes the commands. There's no human on the other end.

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

No branches or pull requests

2 participants