{"thread":{"id":"35774","subject":"Git variable expansion when pulling ?","startedAt":"2014-01-31T17:43:12Z","lastAt":"2014-01-31T17:43:12Z","messageCount":1,"participants":["gabriel staffelbach"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"233987","messageId":"79E8887F-E7DD-4AA5-945B-10D86F317340@cerfacs.fr","threadId":"35774","inReplyTo":null,"subject":"Git variable expansion when pulling ?","fromName":"gabriel staffelbach","fromEmail":"gabriel.staffelbach@cerfacs.fr","sentAt":"2014-01-31T17:43:12Z","receivedAt":"2014-01-31T17:43:12Z","isPatch":false,"sender":{"key":"gabriel.staffelbach@cerfacs.fr","avatar":null},"body":"Hi , \nI’ve just setup a variable expansion scheme via the attribues filters for our versioning purposes. \nI do realise there is much debate on whether to do this or not but it is an indispensable part for our code. \n\nHowever i just realised the filters are not executed if we update the code via a pull command and the file with the metadata is not modified . \n\nIs there a correct way to have the filter execute even for a pull and update the Git sha1 info in our log file ? \n\nThanks\n\nGabriel\n"}]}