OK, cool, but... why? If your goal is release notes with content meaningful to the user, not just tech details, wouldn't it be even easier/better/cheaper to just send the content of Jira tickets instead of all the code into your context? (Or whatever PM system you use to track your product work)
After all, that would include user-meaningful content already as well as priorities and other business context. Why guess information from code when there is probably already a system that has those answers?
Edit: I just saw where you posted this a month ago, too. From that post: "I'm a PM at Arthur. Every release I'd spend hours combing through commit logs and PRs trying to write something coherent for our users. "
Now I'm doubly confused. You are a PM who doesn't track the work? You comb through code? This makes so little sense. That isn't at all typical of how PMs work?
codingdave•3h ago
After all, that would include user-meaningful content already as well as priorities and other business context. Why guess information from code when there is probably already a system that has those answers?
Edit: I just saw where you posted this a month ago, too. From that post: "I'm a PM at Arthur. Every release I'd spend hours combing through commit logs and PRs trying to write something coherent for our users. "
Now I'm doubly confused. You are a PM who doesn't track the work? You comb through code? This makes so little sense. That isn't at all typical of how PMs work?