Skip to content

Commit

Permalink
removing example path from improve prepromt
Browse files Browse the repository at this point in the history
  • Loading branch information
ATheorell committed Dec 25, 2023
1 parent 3da769e commit dacc8fa
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
10 changes: 5 additions & 5 deletions gpt_engineer/preprompts/improve
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Take requests for changes to the supplied code, and then you MUST

You MUST format EVERY code change with an *edit block* like this:
```python
some/dir/example.py
example.py
<<<<<<< HEAD
# some comment
# Func to multiply
Expand All @@ -29,7 +29,7 @@ Also, in the class `DB`, we need to update the "SOMETHING"

OUTPUT:
```python
some/dir/example_1.py
example_1.py
<<<<<<< HEAD
def mul(a,b)
=======
Expand All @@ -38,7 +38,7 @@ some/dir/example_1.py
```

```python
some/dir/example_1.py
example_1.py
<<<<<<< HEAD
def add_one(a,b):
a = a+2
Expand All @@ -49,7 +49,7 @@ some/dir/example_1.py
```

```python
some/dir/example_2.py
example_1.py
<<<<<<< HEAD
class DBS:
db = 'aaa'
Expand All @@ -65,7 +65,7 @@ So edit blocks must be precise and unambiguous!

Every *edit block* must be fenced with ```CONTENT OF EDIT BLOCK``` with the correct code language.

Note that "some/dir/" is a placeholder to be replaced with a relative path to the file. Do not put the placeholder "some/dir/" in a response.
The file name at the top of the edit block (example_1.py in the examples) is the relative path to the file.

The `HEAD` section must be an *exact set of sequential lines* from the file! This is very important. Otherwise the parser won't work.
NEVER SKIP LINES in the `HEAD` section!
Expand Down
2 changes: 1 addition & 1 deletion tests/ai_cache.json

Large diffs are not rendered by default.

0 comments on commit dacc8fa

Please sign in to comment.