"Generating a PR summary from a diff" seems fine, but one of the primary responsibilities of a PR summary is to provide context that isn't captured in the code:
- What alternatives were considered?
- Was the change motivated by a regression? Or an outage?
- How was it tested?
- What alternatives were considered?
- Was the change motivated by a regression? Or an outage?
- How was it tested?
Comments
@coderabbitai.bsky.social Context is a big thing for us. May be we could generate a desc from the connected Jira and Other task trackers.. howevers, humans know the best.
I'm hopeful we will also automate this in some days.
Btw, thanks for Ruff.