Bug 994793 - Require attributted commit messages on content map pushes
Require attributted commit messages on content map pushes
Status: NEW
Product: PressGang CCMS
Classification: Community
Component: CSProcessor (Show other bugs)
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: pressgang-ccms-dev
Depends On:
  Show dependency treegraph
Reported: 2013-08-07 23:03 EDT by Tim Hildred
Modified: 2014-10-26 21:14 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Hildred 2013-08-07 23:03:52 EDT
Description of problem:
csprocessor push does not allow commit messages on push, like the git and svn equivilants do. 

Expected results:
Pushing new content specs should require a message and an attribution. 

In the CLI, something like csprocessor push --m "Re-arranged topics to resolve BZ#123456"

In the UI, just do the same as what you're going to do with other topics, require attribution for every update to a content map, and encourage/require commit messages.
Comment 1 Lee Newson 2013-08-07 23:29:10 EDT
You can already do what you mentioned, however it isn't compulsary and to be honest I'm not sure it should be or not (sending the user who made the change is another thing altogether that I would agree with).

You can also add the "--rev-history" parameter if the log message should be marked as something to be included in an auto generated Revision History.
Comment 2 Lee Newson 2013-08-07 23:36:54 EDT
Just noticed you example was "--m", the double dash notation is used for long parameter names and the single dash notation is a shortened version. So in this case for the commit message it is "--message" or "-m".

Note You need to log in before you can comment on or make changes to this bug.