Would be nice to relax the "commit message rule"

Bug #1205102 reported by Sebastien Bacher
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
jenkins-launchpad-plugin
Confirmed
Medium
Unassigned

Bug Description

The "lack of commit message" is an error that often bites people submitting changes, I would suggest to be a bit more tolerant and let the commit message to be "the message of the commit" when the merge has only 1 commit

Rational:

- if there is one commit, there is no real reason for the message of the merge to be different of the one of the one commit

- there are some people suggesting to use the description has commit, when the commit message is missing, that can be controversial: it's not uncommon to use the description to put review comments or details that are not interesting to the commit

- the most frequent case (especially for new contributors, who are the most likely to overlook the need for a commit message) is to have a trivial change with one commit, we can optimize for that case

summary: - Would be nice to use the relax the "commit message rule"
+ Would be nice to relax the "commit message rule"
description: updated
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

I am all in favor of the one commit means that's the commit message.

Changed in jenkins-launchpad-plugin:
status: New → Confirmed
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.