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

Re: Preventing merges from one branch into others

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 7, 2013, 19:38 UTC
Message-ID
<7v8v6z7w38.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130207131440.716c1022@bigbox.christie.dr>
Tim Chase <git@tim.thechases.com> writes:
> ...  I didn't
> see any sort of "pre-merge" hook script.
http://thread.gmane.org/gmane.comp.version-control.git/94111/focus=71069

I think yours is a canonical example of "I do not want to run command X when these conditions hold", when "these conditions" can be checked locally _before_ you decide to do X.

While it is theoretically possible to give X a pre-X hook in such a case, we do not want it to be the first choice to avoid hook bloat.

Previous: Tim Chase
Message 2 of 2 in “Preventing merges from one branch into others”
  1. Tim ChaseFeb 7, 2013
  2. Junio C HamanoFeb 7, 2013

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.