Changelog support for smart-release (continuation 2) #209

Byron · 2021-09-26T14:15:50Z

Fix for #198.

After merge, release and fix #204, and setup install validation for smart-release.

Using ByteVec consuming trait methods on BString fails with "cannot move out of dereference of BString" BurntSushi/bstr#98
fix: return-values of Commit::footers() and Commit::breaking_description() use lifetime of message… crate-ci/git-conventional#16

…which comes with the benefit of not needing to be parsed back at all. We will just treat it as marker when parsing, knowing that it will be replaced with the same (or updated) information during merge. This allows to create more elaborate statistics without adding effort to parse this back - this effort is spent exlusively where it matters, with the git-conventional sections that are in fact user-editable.

…to help handling parsed/statistical/read-only types even better

…ome (#198)

…atistics (#198)

…instead of also avoiding the changelog to be written. Otherwise statistics wouldn't be updated if its not rewritten. Now that only drives whether or not we get to preview a changelog, which won't happen if there is nothing relevant, like statistics or headline changes.

…parsing really needs a headline and it's probably ok to provide it. Otherwise parsing would be more complicated and it shouldn't be that way now.

…as the latter is hard to keep in line with the markdown, especially if it's markdown itself. Instead, people can click the commit link that github will auto-generate.

…as they forgot to turn off gpg signing.

…which changed due to larger changelogs.

…198)

…and learn that the top-level crate definitely needs another approach for details as it simply is affected by all commits.

Previously when accessing a packed object, it would store the base object into the pack cache (if it wasn't retrieved from there) which is great if that operation is free. Since it isn't, it's better not to stress the cache with puts and trash more objects than necessary. Now only the last decompressed object will be put into the LRU cache.

This really helps with conveniently adjusting the changelog to your needs.

…even though it's not working correctly judging by a few samples.

…to enable dealing with parent lookups specifically.

…which fixes an over-abundance of commits showing up in the details section even though they didn't actually contribute.

…198)

…for some more absolute order of what we would have gotten otheriwse.

…and verify that unparsable inbetweens are bound to their closest parseable headline.

…with it being added only if there is no other section present yet. That way changelogs can be configured intuitively.

With it one can omit auto-generated sections of the given name.

…to allow disabling various changelog segments like clippy, or commit statistics. Note that it's always possible to delete individual sections afterwards.

…which reveals a lot of issues with a few core pieces of logic. Nothing terrible, but some tests need to be written to nail it.

…d want to add (#198)

…atistics (#198)

Byron · 2021-10-03T12:01:38Z

Rollup changes from a week to avoid long-running PRs.

Byron added 30 commits September 26, 2021 22:15

fix docs (#198)

90056c8

Add new section type and write it out: clippy (#198)

37280cd

More robust parsing of read-only sections (#198)

252e84f

refactor… (#198)

6edf196

…to help handling parsed/statistical/read-only types even better

Basic commit statistics with round-trip, more actual information to c…

83e2b2d

…ome (#198)

More commit statistics (#198)

29a01d6

refactor (#198)

bcec911

Fix tests (#198)

ff15c1b

Also provide a duration in days for preparing a release as part of st…

4d36844

…atistics (#198)

thanks clippy

11bd4a3

refactor (#198)

90c304e

Update changelogs (#198)

b30db3b

Add details behind a fold, but… (#198)

3c711f4

…parsing really needs a headline and it's probably ok to provide it. Otherwise parsing would be more complicated and it shouldn't be that way now.

create details headline based on log message (#198)

4eaab37

fix md formatting on github (#198)

f90f3ce

Use message commit id instead of body… (#198)

2746d93

…as the latter is hard to keep in line with the markdown, especially if it's markdown itself. Instead, people can click the commit link that github will auto-generate.

Put commit details to the end of generated segments (#198)

bef2e0e

Update all changelogs with details (#198)

0732699

Stable smart-release journey tests… (#198)

d5b3099

…as they forgot to turn off gpg signing.

boost allowed package sizes… (#198)

c1636e4

…which changed due to larger changelogs.

feat: oid::short_hex(len) for truncated hex representations (#198)

d234b97

Only use short hashes for logs, without detecting ambiguity for now (#…

8d48d59

…198)

Generate changelogs with details (#198)

fd0f3bd

Fixup remaining changelogs… (#198)

0ac488a

…and learn that the top-level crate definitely needs another approach for details as it simply is affected by all commits.

refactor!: rename oid::short_hex() to oid::to_hex() (#198)

deb99b3

adapt to git-hash refactor (#198)

d881734

The first headline level controls all the other ones (#198)

302b267

This really helps with conveniently adjusting the changelog to your needs.

Byron added 20 commits September 28, 2021 10:03

refactor and improve path filtering to find relevant commits… (#198)

99db079

…even though it's not working correctly judging by a few samples.

Use hashmap based lookup for trees… (#198)

55d2d17

…to enable dealing with parent lookups specifically.

Use most relevant parent tree for change comparison… (#198)

6d02ac8

…which fixes an over-abundance of commits showing up in the details section even though they didn't actually contribute.

greatly reduce changelog size now that the traversal fix is applied (#…

3924c03

…198)

Sort all commits by time, descending… (#198)

7c37a3d

…for some more absolute order of what we would have gotten otheriwse.

reorder headlines according to version ordering… (#198)

733d7f1

…and verify that unparsable inbetweens are bound to their closest parseable headline.

Rebuild all changelogs to assure properly ordered headlines (#198)

cfcaa66

thanks clippy

b693e62

Easy removal of statistical sections, by just removing them… (#198)

dce113d

…with it being added only if there is no other section present yet. That way changelogs can be configured intuitively.

feat: changelog command learns the --without <section> option (#198)

1df3ad7

With it one can omit auto-generated sections of the given name.

feat: smart-release with --changelog-without option… (#198)

7db19a8

…to allow disabling various changelog segments like clippy, or commit statistics. Note that it's always possible to delete individual sections afterwards.

thanks clippy

738538c

Update changelogs just for fun

fa91ba3

refactor (#198)

46dc207

Sketch out data structure for git-conventional segments (#198)

b85ba9a

basic generation of git-conventional information (#198)

8bf5452

Quick and dirty writing of conventional messages… (#198)

6de3e03

…which reveals a lot of issues with a few core pieces of logic. Nothing terrible, but some tests need to be written to nail it.

merge doesn't consider user generated sections, only the ones it woul…

a71b28a

…d want to add (#198)

assure git-conventional is treated like user generated content for st…

5afce3a

…atistics (#198)

thanks clippy

d5720f5

Byron merged commit af9d137 into main Oct 3, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Changelog support for smart-release (continuation 2) #209

Changelog support for smart-release (continuation 2) #209

Byron commented Sep 26, 2021 •

edited

Loading

Byron commented Oct 3, 2021

Changelog support for smart-release (continuation 2) #209

Changelog support for smart-release (continuation 2) #209

Conversation

Byron commented Sep 26, 2021 • edited Loading

Byron commented Oct 3, 2021

Byron commented Sep 26, 2021 •

edited

Loading