patchwork
patchwork copied to clipboard
Automate development gruntwork like code reviews, patching and documentation with LLM workflows.
Added more language files.
At the moment we only retrieve the body and comments from an Issue as shown here - https://github.com/patched-codes/patchwork/blob/main/patchwork/common/client/scm.py#L303 If the body is empty and there are no comments it will...
In the PR the links to file and the changes are not correct. E.g. https://github.com/codelion/dvpwa/pull/16 The link on /Users/user/Documents/GitHub/dvpwa/docker-compose.yml is pointing to https://github.com/codelion/dvpwa/pull/16/files#diff-73d2c5aa8a84b134c0d026689a5fd1fcf3b6696d87236126c2f1d6c5c0a53573 instead of https://github.com/codelion/dvpwa/pull/16/files#diff-e45e45baeda1c1e73482975a664062aa56f20c03dd9d64a827aba57775bed0d3
Can we remove the link to the summary here below the File changed. It points to the same URL as the File Changed does.
E.g. in CallOpenAI step we can wrap this loop (https://github.com/patched-codes/patchwork/blob/master/patchwork/steps/CallOpenAI/CallOpenAI.py#L47) with tqdm to get a nice progress bar.
- Create a new patchflow that given a folder will generate docstrings for all the methods in the source files (Python/Java).
Allow users to specify the criteria (in natural language) that is used for PRReview. This will become part of the prompt and be sent to the LLM before generating the...
This pull request from patchwork fixes 4 vulnerabilities. ------ * File changed: [/home/runner/work/patchwork/patchwork/pyproject.toml](https://github.com/patched-codes/patchwork/pull/675/files#diff-818dc3f964862e7cbb1fe7c5071616c54a1d89832281c9df9992429ca3c78a8e)