Fixing PgbackrestRetention.History processing - #43
Conversation
Agalin
left a comment
There was a problem hiding this comment.
Thanks for the fix, looks promising.
|
Commit lint doesn't like your commit message: Should be something like this: Also commit must be signed off. |
3ebf586 to
1eb0da8
Compare
|
Thanks for adding the signed off section. It still won't pass the type and subject checks. |
6c9cdf3 to
c9f4972
Compare
|
Hi @Agalin , I'm confused now. What does this linter want? I've provided type, lower-case starting subject, sign-off, and even message body. Best regards, |
|
It wants you to squash everything. 🙂 Goes through each commit and found some not matching rules. Try squashing everything with this as the commit header / first line: It should pass for all rules related to the first line. Rest of the commit was fine already. |
|
You mean squash several commits into one OR basically remove message body and leave subject with type and sign-off? |
|
Not Its body is always acceptable as long as it includes the signed-off line (empty body generates only a warning). For example, this commit contains a valid body. Linter is really careful because those commits are then used to generate release notes and to determine version bumps. |
c9f4972 to
fb557f3
Compare
Signed-off-by: Boris Mironov <boris_mironov@outlook.com>
fb557f3 to
8adaf2d
Compare
|
squashed everything as much as possible |
Hi @Agalin ,
I believe this Pull Request fixes Issue #35 . The actual issue was in a way of processing
.retention.Historyininternal/pgbackrest/command/commandbuilder.go:143. On top of this line I've also added a few tests to cover this area.Please accept at your convenience.
Best regards,
Boris