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

Re: Server-side preventing some files from being overwritten

From
Jakub Narębski <jnareb@gmail.com>
Date
Jul 21, 2016, 11:21 UTC
Message-ID
<5790B055.4060603@gmail.com>
In-Reply-To
<CAGZ79kb=2rpYucjhavNB_XHLk9rjKSoHzL9bwM5buDO0GyW3vw@mail.gmail.com>
W dniu 2016-07-14 o 18:57, Stefan Beller pisze:
Show 7 quoted lines
> On Thu, Jul 14, 2016 at 8:31 AM, Thorsten Glaser <t.glaser@tarent.de> wrote:
>> Hi *,
>>
>> is there a way, for example with some sort of pre-receive hook,
>> to prevent some files from being overwritten by a push?
> 
> pre-receive hooks are a thing!

Or you can use third-party tools with support for such cases, such as Gitolite. VREFs allow to restrict pushes by the filename, see http://gitolite.com/gitolite/vref.html#NAME (though I am not sure if it checks only the end state, or if it checks every commit that was pushed).

Best,
-- 
Jakub Narębski
Previous: Junio C HamanoNext: Thorsten Glaser
Message 11 of 12 in “Server-side preventing some files from being overwritten”
  1. Thorsten GlaserJul 14, 2016
  2. Stefan BellerJul 14, 2016
  3. Thorsten GlaserJul 14, 2016
  4. Junio C HamanoJul 14, 2016
  5. Junio C HamanoJul 14, 2016
  6. Stefan BellerJul 14, 2016
  7. Ævar Arnfjörð BjarmasonJul 15, 2016
  8. Thorsten GlaserJul 15, 2016
  9. Thorsten GlaserJul 14, 2016
  10. Junio C HamanoJul 14, 2016
  11. Jakub NarębskiJul 21, 2016
  12. Thorsten GlaserJul 21, 2016

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.