-
OneDev
changed state to 'Closed' 3 years ago
Previous Value Current Value Open
Closed
-
State changed as code fixing the issue is committed (7fcb16e6)
-
OneDev
changed state to 'Released' 3 years ago
Previous Value Current Value Closed
Released
-
State changed as build #3693 is successful
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee |
Issue Votes (0)
Conventional commits does not specify the revert commit. See: https://github.com/conventional-commits/conventionalcommits.org/issues/88
They recommend using a
reverttype as it matches the current spec but do not force it. This is kind of fine if you use git on command line since by defaultgit revertlets you edit the commit message. However many people are using Git UI tools which do not allow editing the message right away when reverting a commit and the tool uses the default git message which isAsking developers to manually change the message from
Revert "fix(core): some text"torevert: fix(core): some textjust to satisfy the spec could feel like useless extra work, as the default git behavior is already pretty good. Especially in UI tools it requires some extra clicks to do so.So I think OneDev should always allow the default git revert message for simplicity and good out of the box behavior.