Bug 1609363
Summary: | the comment on github job should post full commit message to issue. | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Amar Tumballi <atumball> |
Component: | project-infrastructure | Assignee: | bugs <bugs> |
Status: | CLOSED DEFERRED | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | mainline | CC: | amukherj, bugs, gluster-infra, jeff, sankarshan, srangana |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | Process-Automation | ||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-27 00:49:32 UTC | 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
Amar Tumballi
2018-07-27 18:36:43 UTC
I'm not sure if this useful. Even the bugzilla check only links title until the merge comes along. At that point we post the whole thing. My 2 c's: - Commit subject appears twice, once due to posting and once merged as github picks up the reference to the "Fixes"/"Updates" keywords - Commit message in whole can be useful to understand more details, than going to the patch - So having the job post the entire message can be useful and also possibly drive better commit message writing as an aside The downsides could be claims that the commit message itself provides the required documentation and such, which we should avoid. I would prefer the entire message than just the subject, unless there are considerations that I am missing. |