Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commit message lists all historical charts, not just new
Low Severity
The
ls tracebloc-*.tgzin the commit message runs on thegh-pagesbranch, which accumulates.tgzfiles from all previous releases. As releases build up, this commit message will list every historical chart file (e.g., "Release helm chart(s): tracebloc-1.0.0.tgz tracebloc-2.0.0.tgz tracebloc-2.0.1.tgz") rather than just the newly released one. Thetr '\n' ' 'flattening makes this worse than the old code, where newlines caused git to split the message so only the first filename appeared in the commit subject. The message grows unboundedly with each release.