git/list[1] front-page[2] threads[3] people[4] search[5] about
 

A git hook that does git cherry-pick and push automatically

From
RXRay Xie <samuiotoko925@gmail.com>
Date
Mar 20, 2015, 04:07 UTC
Message-ID
<CAA4Z6SXzekMdPgKKaXqAObPcpFXDWpaQvNhJg6DEsOxbMOy3Lw@mail.gmail.com>

So today I had a shocking moment while I was doing my cherry-pick, after I performed all the pre-checkin duties (the usual build the code, run the test to make sure the cherry-pick infact works), I found out that my original commit was already cherry-picked, then I found out someone in engineering make the decision to do an automate cherry-pick from that branch to another so he added a git hook to run do cherry-pick and push on every commit, yes, a simple cherry-pick then push; mind you, these are not feature / dev branch, these are release branches, both of them.

Then after I came back from the shock, made a big protest about how this is the worst thing I have seen and I will never live with it, and that's why "git cherry-pick" and "git push" are 2 separate commands, as any reasonable developer, you do your very best to ensure you are not pushing something that is fundamentally broken; however for the life of me and talk these few people into senses.

So, I am sending this to seek for some expert advice how I can drive some sense into these people so they don't screw up my life as an developer.

Regards, Desperate developer, Ray.

Next: David Aguilar
Message 1 of 4 in “A git hook that does git cherry-pick and push automatically”
  1. Ray XieMar 20, 2015
  2. David AguilarMar 20, 2015
  3. Ray XieMar 20, 2015
  4. Stefan BellerMar 20, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.