How Do We Extract the “Why” from a PR into a CHANGELOG with Jev? 🤔

Description and use

<p>Hoi hoi! 👋</p> <p>I'm <a class="mentioned-user" href="https://dev.to/nyaomaru">@nyaomaru</a>, a frontend engineer currently building an AI-assisted CHANGELOG generator and experimenting with Jev. 😸</p> <p>Recently, I have been thinking about one problem.</p> <p>How can we extract this<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight markdown"><code><span class="gu">## Why</span> The previous implementation could leave stale release data after an update. </code></pre> </div> <p>from a pull request and put it into a CHANGELOG?<br> </p> <div class="highlight js-code-h

Problem

<p>Hoi hoi! 👋</p> <p>I'm <a class="mentioned-user" href="https://dev.to/nyaomaru">@nyaomaru</a>, a frontend engineer currently building an AI-assisted CHANGELOG generator and experimenting with Jev. 😸</p> <p>Recently, I have been thinking about one problem.</p> <p>How can we extract this<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight markdown"><code><span class="gu">## Why</span> The previous implementation could leave stale release data after an update. </code></pre> </div> <p>from a pull request and put it into a CHANGELOG?<br> </p> <div class="highlight js-code-h

Outcome

<p>Hoi hoi! 👋</p> <p>I'm <a class="mentioned-user" href="https://dev.to/nyaomaru">@nyaomaru</a>, a frontend engineer currently building an AI-assisted CHANGELOG generator and experimenting with Jev. 😸</p> <p>Recently, I have been thinking about one problem.</p> <p>How can we extract this<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight markdown"><code><span class="gu">## Why</span> The previous implementation could leave stale release data after an update. </code></pre> </div> <p>from a pull request and put it into a CHANGELOG?<br> </p> <div class="highlight js-code-h

Evidence

How Do We Extract the “Why” from a PR into a CHANGELOG with Jev? 🤔

Source