Page MenuHomePhabricator

Include commit hash in log message for every sync
Open, LowPublic

Description

Sometimes we just see, eg:
22:58 logmsgbot: ebernhardson synchronized php-1.23wmf15/extensions/Flow/

Where others give more information:
00:17 logmsgbot: ori synchronized php-1.23wmf16/extensions/CentralNotice 'Update CentralNotice to tip of wmf_deploy for I7d8259fc4'

The easy bit of extra info that could be included automatically is the hash associated with the latest commit for what is being sync'd.

Details

Reference
bz62340

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 3:06 AM
bzimport added a project: Deployments.
bzimport set Reference to bz62340.
bzimport added a subscriber: Unknown Object (MLST).

(In reply to Greg Grossmeier from comment #0)

The easy bit of extra info that could be included automatically is the hash
associated with the latest commit for what is being sync'd.

  1. Do we want to exclude the hash entirely if the HEAD is a security patch or should it show the latest origin commit?
  1. How would you like the message to be formatted? "Synchronized <path> <hash>: <message>" or maybe "Synchronized <path>: <message> (<hash>)"?
greg renamed this task from Include commit hash for every synch to Include commit hash for every sync.Feb 10 2016, 12:02 AM
greg updated the task description. (Show Details)
greg edited projects, added scap2; removed Deployments.
greg set Security to None.
greg removed a subscriber: wikibugs-l-list.
greg renamed this task from Include commit hash for every sync to Include commit hash in log message for every sync.Apr 4 2016, 8:52 PM