mirror of
https://github.com/restic/restic.git
synced 2024-12-21 23:33:03 +00:00
Changelogs should omit problem if it duplicates the new behavior
When adding a new feature, the problem description often just says that feature Y was missing, followed by saying that feature Y is now supported. This duplication just makes the changelog entries unnecessarily verbose.
This commit is contained in:
parent
efec1a5e96
commit
7680f48258
1 changed files with 2 additions and 0 deletions
|
@ -5,6 +5,8 @@ Enhancement: Allow custom bar in the foo command
|
|||
|
||||
# Describe the problem in the past tense, the new behavior in the present
|
||||
# tense. Mention the affected commands, backends, operating systems, etc.
|
||||
# If the problem description just says that a feature was missing, then
|
||||
# only explain the new behavior.
|
||||
# Focus on user-facing behavior, not the implementation.
|
||||
# Use "Restic now ..." instead of "We have changed ...".
|
||||
|
||||
|
|
Loading…
Reference in a new issue