DEV: patchbot: add the AI-based bot to pre-select candidate patches to backport
This is a set of scripts, prompts and howtos to have an LLM read commit
messages and determine with great accuracy whether the patch's author
intended for the patch to be backported ASAP, backported after some time,
not backported, or unknown state. It provides all this in an interactive
interface making it easy to adjust choices and proceed with what was
selected. This has been improving over the last 9 months, as helped to
spot patches for a handful of backport sessions, and was only limited by
usability issues (UI). Now that these issues are solved, let's commit the
tool in its current working state. It currently runs every hour in a
crontab for me and started to prove useful since the last update, so it
should be considered in a usable state now, especially since this latest
update reaches close to 100% accuracy compared to a human choice, so it
saves precious development time and may allow stable releases to be
emitted more regularly.
There's detailed readme, please read it before complaining about the
ugliness of the UI :-)
2023-12-18 19:41:41 +00:00
|
|
|
|
|
|
|
|
ENDINPUT
|
|
|
|
|
BEGININSTRUCTION
|
|
|
|
|
|
|
|
|
|
You are an AI assistant that follows instruction extremely well. Help as much
|
|
|
|
|
as you can, responding to a single question using a single response.
|
|
|
|
|
|
|
|
|
|
The developer wants to know if he needs to backport the patch above to fix
|
|
|
|
|
maintenance branches, for which branches, and what possible dependencies might
|
|
|
|
|
be mentioned in the commit message. Carefully study the commit message and its
|
|
|
|
|
backporting instructions if any (otherwise it should probably not be backported),
|
|
|
|
|
then provide a very concise and short summary that will help the developer decide
|
|
|
|
|
to backport it, or simply to skip it.
|
|
|
|
|
|
|
|
|
|
Start by explaining in one or two sentences what you recommend for this one and why.
|
|
|
|
|
Finally, based on your analysis, give your general conclusion as "Conclusion: X"
|
|
|
|
|
where X is a single word among:
|
|
|
|
|
- "yes", if you recommend to backport the patch right now either because
|
|
|
|
|
it explicitly states this or because it's a fix for a bug that affects
|
2024-05-29 12:38:21 +00:00
|
|
|
a maintenance branch (3.0 or lower);
|
DEV: patchbot: add the AI-based bot to pre-select candidate patches to backport
This is a set of scripts, prompts and howtos to have an LLM read commit
messages and determine with great accuracy whether the patch's author
intended for the patch to be backported ASAP, backported after some time,
not backported, or unknown state. It provides all this in an interactive
interface making it easy to adjust choices and proceed with what was
selected. This has been improving over the last 9 months, as helped to
spot patches for a handful of backport sessions, and was only limited by
usability issues (UI). Now that these issues are solved, let's commit the
tool in its current working state. It currently runs every hour in a
crontab for me and started to prove useful since the last update, so it
should be considered in a usable state now, especially since this latest
update reaches close to 100% accuracy compared to a human choice, so it
saves precious development time and may allow stable releases to be
emitted more regularly.
There's detailed readme, please read it before complaining about the
ugliness of the UI :-)
2023-12-18 19:41:41 +00:00
|
|
|
- "wait", if this patch explicitly mentions that it must be backported, but
|
|
|
|
|
only after waiting some time.
|
|
|
|
|
- "no", if nothing clearly indicates a necessity to backport this patch (e.g.
|
|
|
|
|
lack of explicit backport instructions, or it's just an improvement);
|
|
|
|
|
- "uncertain" otherwise for cases not covered above
|
|
|
|
|
|
|
|
|
|
ENDINSTRUCTION
|
|
|
|
|
|
|
|
|
|
Explanation:
|