view mercurial/templates/spartan/changelogentry.tmpl @ 33698:3748098d072a

releasenotes: add similarity check function to compare incoming notes It is possible that the incoming note fragments have some similar content as the existing release notes. In case of a bug fix, we match for issueNNNN in the existing notes. For other general cases, it makes use of fuzzywuzzy library to get a similarity score. If the score is above a certain threshold, we ignore the fragment, otherwise add it. But the score might be misleading for small commit messages. So, it uses similarity function only if the length of string (in words) is above a certain value. The patch adds tests related to its usage. But it needs improvement in the sense of combining incoming notes. We can use interactive mode for adding notes. Maybe we can do this if similarity is under a certain range.
author Rishabh Madan <rishabhmadan96@gmail.com>
date Sat, 05 Aug 2017 05:25:36 +0530
parents a65714215377
children a1de4ffaa7a8
line wrap: on
line source

<table class="logEntry parity{parity}">
 <tr>
  <th class="label"><span class="age">{date|rfc822date}</span>:</th>
  <th class="firstline">{desc|strip|firstline|escape|nonempty}</th>
 </tr>
 <tr>
  <th class="revision">changeset {rev}:</th>
  <td class="node"><a href="{url|urlescape}rev/{node|short}{sessionvars%urlparameter}">{node|short}</a></td>
 </tr>
 {parent%changelogparent}
 {child%changelogchild}
 {changelogtag}
 <tr>
  <th class="author">author:</th>
  <td class="author">{author|obfuscate}</td>
 </tr>
 <tr>
  <th class="date">date:</th>
  <td class="date">{date|rfc822date}</td>
 </tr>
 <tr>
  <th class="files"><a href="{url|urlescape}file/{node|short}{sessionvars%urlparameter}">files</a>:</th>
  <td class="files">{files}</td>
 </tr>
</table>