Bug 994793

Summary:	Require attributted commit messages on content map pushes
Product:	[Community] PressGang CCMS	Reporter:	Tim Hildred <thildred>
Component:	CSProcessor	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	1.x
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tim Hildred 2013-08-08 03:03:52 UTC

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-08 03:29:10 UTC

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-08 03:36:54 UTC

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".