From 4863df689877d0628520a10346c6ad7cbb7cd9cd Mon Sep 17 00:00:00 2001 From: Hemang Joshi Date: Fri, 14 Apr 2023 10:27:32 +0530 Subject: [PATCH 1/2] added `star-history` added `star-history` --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 55813f7..7df05b7 100644 --- a/README.md +++ b/README.md @@ -36,3 +36,7 @@ This is just a quick prototype I threw together in a few hours. There are many p - multiple files / codebases: send GPT everything that appears in the stacktrace - graceful handling of large files - should we just send GPT relevant classes / functions? - extension to languages other than python + +## Star History + +[![Star History Chart](https://api.star-history.com/svg?repos=biobootloader/wolverine&type=Date)](https://star-history.com/#biobootloader/wolverine) From 6afb4db2ffc7878e2a125cd53917a1abfacb8790 Mon Sep 17 00:00:00 2001 From: Ikko Eltociear Ashimine Date: Fri, 14 Apr 2023 16:37:05 +0900 Subject: [PATCH 2/2] fix typo in README.md reliablity -> reliability --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 55813f7..0a8cae3 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,7 @@ This is just a quick prototype I threw together in a few hours. There are many p - add flags to customize usage, such as asking for user confirmation before running changed code - further iterations on the edit format that GPT responds in. Currently it struggles a bit with indentation, but I'm sure that can be improved -- a suite of example buggy files that we can test prompts on to ensure reliablity and measure improvement +- a suite of example buggy files that we can test prompts on to ensure reliability and measure improvement - multiple files / codebases: send GPT everything that appears in the stacktrace - graceful handling of large files - should we just send GPT relevant classes / functions? - extension to languages other than python